Skip to main content
POST
Exchange OAuth grants for opaque access tokens

Authorizations

Authorization
string
header
required

Use client_id as username and client_secret as password for confidential server-side calls. The application allowed_scopes still gate each /v2 endpoint; never use this secret in browsers, mobile apps, logs, or query strings. Server integrations may alternatively send x-client-id and x-client-secret headers (the legacy x-invoiceedge-* names remain accepted).

Body

application/x-www-form-urlencoded
grant_type
enum<string>
required
Available options:
client_credentials,
authorization_code,
refresh_token
scope
string

Required for client_credentials and authorization_code requests. Optional on refresh_token to narrow the refreshed access token.

Example:

"products.read categories.read vendors.read locations.read"

code
string
redirect_uri
string<uri>
code_verifier
string
refresh_token
string

Response

Opaque bearer token response.

access_token
string
required
token_type
string
required
Example:

"Bearer"

expires_in
integer
required
Example:

3600

scope
string
required
Example:

"products.read categories.read vendors.read locations.read"

refresh_token
string