OAuth Scopes and Endpoints
Required Scopes and Endpoint Domains for Sage Intacct
When integrating with Sage Intacct, your application needs specific permissions to interact with the API.These permissions are defined by access scopes, which determine what data your application can access and what actions it can perform.
This topic provides information about the required access scopes and endpoint domains for the Sage Intacct connector.
Understanding Scopes
Scopes are a way to limit an application's access to a user's data. They define the specific actions that an application can perform on behalf of the user.
For example, a read-only scope might allow an application to view data, while a full access scope might allow it to modify data.
Required Scopes for Sage Intacct
No scopes are required for this connector.Understanding Endpoint Domains
Endpoint domains are the specific URLs that the application needs to communicate with in order to authenticate, retrieve records, and perform other essential operations.
Allowlisting these domains ensures that the network traffic between your application and the API is not blocked by firewalls or security settings.
Note: Most users do not need to make any special configurations. Allowlisting is typically only necessary for environments with strict security measures, such as restricted outbound network traffic.
Required Endpoint Domains for Sage Intacct
Domain | Always Required | Description |
<URL> | TRUE | The URL through which Sage Intacct API resources are requested. The default value is https://api.intacct.com/ia/xml/xmlgw.phtml. |
<SSOLoginURL> | FALSE | The login URL of your SSO provider. Required when AuthScheme is set to OKTA. |
<intacct.com> | FALSE | The reply URL that Okta redirects you to upon authenticating. Required when AuthScheme is set to OKTA. |