The APIs use industry standard OAuth2 for authentication. Most users find success with one of the libraries on the OAuth2 website. The following URLs can be used when using an off-the-shelf OAuth2 library:Documentation Index
Fetch the complete documentation index at: https://docs.paxos.com/llms.txt
Use this file to discover all available pages before exploring further.
| Environment | Root URL | Full Path |
|---|---|---|
| Sandbox | https://oauth.sandbox.paxos.com | https://oauth.sandbox.paxos.com/oauth2/token |
| Production | https://oauth.paxos.com | https://oauth.paxos.com/oauth2/token |
➊ Add Scopes (Client Permissions)
When authenticating, include the scopes (Client Permissions) necessary for the client to complete the intended actions.Scopes for each endpoint are listed in the Authorizations section in the API Reference docs. The Market Data and most Pricing endpoints do not require authorization.For example, the following scopes (space delimited) should provide sufficient permissions to mint, redeem, and convert Paxos-issued stablecoins:
➋ Get Access Token
Every endpoint that requires a Scope must be accompanied by an “Authorization” header with a value that follows the \"Bearer {access_token}" schema.
Sandbox
To authenticate with https://oauth.sandbox.paxos.com/oauth2/token, use your credentials to create a bearer token. The authentication request must include{client_id} (Client ID) and {client_secret} (Client Secret) configured for your API credentials.
Include sufficient {client_scopes} (Client Permissions).
Production
To authenticate with https://oauth.paxos.com/oauth2/token, use your credentials to create a bearer token. The authentication request must include the{client_id} (Client ID) and {client_secret} (Client Secret) configured for your API credentials.
Include sufficient {client_scopes} (Client Permissions).
access_token to use in the request authorization header (-H "Authorization: Bearer {access_token}").
access_token, make an API call in Sandbox.