cloudnumbering API v1.1 uses OAuth 2.0 client credentials. Your integration exchanges a client ID and client secret for a bearer access token, then sends that token with each request.
Before you start
Create API client credentials and store the client secret in a secrets manager. The portal shows it only once.
Set up authentication
For the runnable token request, the Authorization header format, token renewal, and secure credential handling, see Authenticate API v1.1 requests in the developer documentation.
Note: The token endpoint accepts credentials as query parameters. Configure clients, proxies, and monitoring tools to redact query strings.
Troubleshooting
The token endpoint returns invalid_client
Check the client ID and client secret. If the secret is unavailable or the credential has been deactivated, create new credentials.
An API request returns invalid_token
Request a new access token and check that the header starts with Authorization: Bearer .
Comments
0 comments
Article is closed for comments.