Sage Intacct · Authentication Profile

Intacct Authentication

Authentication

Sage Intacct secures its APIs with oauth2, openIdConnect, and apiKey across 2 declared security schemes, as derived from its OpenAPI definitions. OAuth 2.0 is offered via the authorizationCode, clientCredentials, and token-exchange flow(s).

CompanyAccountingERPFinancial ManagementCloud AccountingInvoicingPaymentsSaaSREST APIOAuth
Methods: oauth2, openIdConnect, apiKey Schemes: 2 OAuth flows: authorizationCode, clientCredentials, token-exchange API key in:

Security Schemes

OAuth2 / OpenID Connect (REST) openIdConnect
XML Web Services session (legacy) apiKey
scheme: session-credentials · in: body ()

Source

Authentication Profile

intacct-authentication.yml Raw ↑ 
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
summary:
  types: [oauth2, openIdConnect, apiKey]
  oauth2_flows: [authorizationCode, clientCredentials, token-exchange]
  notes: >-
    The modern REST API authenticates with OAuth 2.0 / OpenID Connect (issuer
    https://api.intacct.com). The legacy XML Web Services API uses session-based
    authentication with sender credentials (senderId/senderPassword) plus user
    login (companyId/userId/userPassword) exchanged for a session id.
schemes:
- name: OAuth2 / OpenID Connect (REST)
  type: openIdConnect
  openIdConnectUrl: https://api.intacct.com/.well-known/openid-configuration
  issuer: https://api.intacct.com
  authorizationUrl: https://api.intacct.com/ia/authorize
  tokenUrl: https://api.intacct.com/ia/api/v1/oauth2/token
  jwks_uri: https://api.intacct.com/.well-known/jwks.json
  grant_types: [authorization_code, client_credentials, urn:ietf:params:oauth:grant-type:token-exchange]
  response_types: [code, token, id_token]
  token_endpoint_auth_methods: [client_secret_basic, client_secret_post, private_key_jwt]
  id_token_signing_alg: [RS256]
  sources: [well-known/intacct-openid-configuration.json]
- name: XML Web Services session (legacy)
  type: apiKey
  in: body
  scheme: session-credentials
  description: >-
    Sender-level credentials (senderId + senderPassword) authorize the application;
    a user login (companyId, userId, userPassword) returns a sessionid used on
    subsequent XML requests. Documented at developer.intacct.com.
  sources: [https://developer.intacct.com/web-services/]