Log inTalk to us
Developer tools

Exchange a session token or use client credentials

post/v1/oauth/token
No authentication

For an app's backend, which authenticates as the app with its client_id (the app's id) and client_secret, by HTTP Basic or in the body. Send application/x-www-form-urlencoded. grant_type urn:ietf:params:oauth:grant-type:token-exchange with a subject_token (a session token for this app) returns a 10 minute access token for the same user, install and project, never wider; grant_type client_credentials with install_id returns the install's own token, with no user. Optional scope narrows either. Errors use the RFC 6749 body {error, error_description}.

Returns · 200

  • access_tokenstringRequired
  • token_typestringRequired
    Bearer.
  • expires_inintegerRequired
  • scopestringRequired
  • issued_token_typestring | null
    urn:ietf:params:oauth:token-type:access_token, for a token exchange.
POST /v1/oauth/token
curl --fail-with-body -X POST "https://api.ivoracharge.com/v1/oauth/token"
Response · 200JSON
{
  "access_token": "string",
  "token_type": "string",
  "expires_in": 1,
  "scope": "string",
  "issued_token_type": "string"
}
Requires an approved production API keyProduction access starts with a request, a short meeting with Ivora and a card on file, after which Ivora staff grant your account access. How to request access
Try itproduction · api.ivoracharge.com

This operation needs no API key.

POST is a write: you confirm the method, path and project before it is sent, with a generated Idempotency-Key.