Skip to main content
Most API endpoints require authentication with a Client ID and Secret. Each Client ID has a specific set of allowed scopes (Permissions) to access API endpoints. Scopes allowed on an API client are accessed through the Dashboard Admin > API Management section. To add or remove a scope from an existing API credential, you must create new API credentials.
Contact your Entity Manager if you need permissions to manage API credentials.
When setting scopes, Paxos recommends following the principle of least privilege and only allow scopes required by a specific application. 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. Once the credentials are activated, most users find success using one of the libraries on the OAuth2 website for authentication.
To add or modify API Credentials, you’ll need a Developer or other role with appropriate permissions. Contact your Entity Manager for help.

Add API Credentials

  1. Log in to your Dashboard account and go to Developer > API (API Management).
The API Management page listing saved API credentials, with the API Credential button in the top right
  1. Click API Credential.
  2. Enter a Nickname for your API credentials.
  3. Select the Scopes for your Client ID. For example, the following scopes (space delimited) should be adequate to convert Paxos-issued stablecoins:
  1. Optional: Add Allowable IPs. If you have a single IP address, you can configure a CIDR entry to specify a single IP with 32 fixed bits by appending /32 to the address. For example, using 000.000.0.000/32 will allow only the IP address 000.000.0.000.
Organization Administrators can also configure an organization-wide IP restriction that applies to all credentials. See Organization Settings.
The Create API Credential form with a nickname, selected read and write scopes, and an allowable IP entry
  1. Optional: Enable Request Signing.
  2. Optional: Adjust Advanced Settings (Token Endpoint Auth Method, Grant Types, Redirect URIs). Leave these at their defaults unless a specific integration requires otherwise — see Advanced Settings.
  3. Click Save API Credential. If your organization has an approval policy for API credentials, the button reads Submit for Approval and the credentials are not active until an approver approves the request.
  4. Copy the Client ID and Client Secret and store them in a safe place. The secret will not be displayed in the UI again, and it will have to be reset if forgotten.
The API Details window showing the client scopes, Client ID, and a Client Secret with a warning that the secret is not shown again

Advanced Settings

Most credentials don’t need these — leave them at their defaults. Change them only when a specific integration requires it, such as SCIM or another third-party OAuth integration.

Update or Delete Credentials

To make changes to an existing client, click View next to it in the credentials list, then click Edit or Delete.