Sage Intacct · OAuth Scopes

Sage Intacct OAuth Scopes

OAuth 2.0 searched

Sage Intacct publishes 4 OAuth 2.0 scopes via the authorizationCode, clientCredentials, and tokenExchange flows. Scopes are the fine-grained permissions an application requests at authorization time to act against the Sage Intacct API on a user’s behalf.

Tokens are issued from https://api.intacct.com/ia/api/v1/oauth2/token.

This index is generated from the provider’s OpenAPI security definitions (and, where available, its documented scope reference) and refreshes on every APIs.io network build. Browse every provider’s scopes at scopes.apis.io.

CompanyAccountingERPFinancial ManagementCloud AccountingInvoicingPaymentsSoftware-as-a-ServiceREST APIAuthentication

Scopes: 4 Flows: authorizationCode, clientCredentials, tokenExchange Method: searched

OAuth endpoints

Authorization URL
https://api.intacct.com/ia/authorize

Token URL
https://api.intacct.com/ia/api/v1/oauth2/token

Flows
authorizationCodeclientCredentialstokenExchange

Scopes (4)

Scope	Description	Flows
openid	Request an OpenID Connect ID token identifying the authenticated user/company.	authorizationCode
offline_access	Issue a refresh token so the client can obtain new access tokens without user interaction.	authorizationCode
sage/ai-agents	Grant AI agents / MCP clients governed access to Sage Intacct data via the AI Gateway.	authorizationCode, clientCredentials, tokenExchange
token-exchange	Permit RFC 8693 OAuth 2.0 token exchange (delegation/impersonation) for downstream calls.	tokenExchange

📄 Provider scope reference: https://developer.sage.com/intacct/docs/1/sage-intacct-rest-api/api-essentials

Source

OAuth Scopes

generated: '2026-07-19'
method: searched
source: https://api.intacct.com/.well-known/openid-configuration
docs: https://developer.sage.com/intacct/docs/1/sage-intacct-rest-api/api-essentials
schemes:
- name: OAuth2 / OpenID Connect
  source: well-known/intacct-openid-configuration.json
  issuer: https://api.intacct.com
  flows:
  - flow: authorizationCode
    authorizationUrl: https://api.intacct.com/ia/authorize
    tokenUrl: https://api.intacct.com/ia/api/v1/oauth2/token
  - flow: clientCredentials
    tokenUrl: https://api.intacct.com/ia/api/v1/oauth2/token
  - flow: tokenExchange
    tokenUrl: https://api.intacct.com/ia/api/v1/oauth2/token
scopes:
- scope: openid
  description: Request an OpenID Connect ID token identifying the authenticated user/company.
  flows: [authorizationCode]
  sources: [well-known/intacct-openid-configuration.json]
- scope: offline_access
  description: Issue a refresh token so the client can obtain new access tokens without user interaction.
  flows: [authorizationCode]
  sources: [well-known/intacct-openid-configuration.json]
- scope: sage/ai-agents
  description: Grant AI agents / MCP clients governed access to Sage Intacct data via the AI Gateway.
  flows: [authorizationCode, clientCredentials, tokenExchange]
  sources: [well-known/intacct-openid-configuration.json]
- scope: token-exchange
  description: Permit RFC 8693 OAuth 2.0 token exchange (delegation/impersonation) for downstream calls.
  flows: [tokenExchange]
  sources: [well-known/intacct-openid-configuration.json]

Work with this as data

Every scope set here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for oauth scopes

4 MCP tools reach this

find_scopesBrowse and filter every scope set in the catalog.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.

All 92 tools →

Call it yourself

curl for this page

This scope set

curl "https://apis.io/api/v1/scopes/intacct-scopes"

All oauth scopes

curl "https://apis.io/api/v1/scopes?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.