Authentication
Beta uses the OAuth2 client-credentials grant type to authenticate access to secure resources.
Last updated
Beta uses the OAuth2 client-credentials grant type to authenticate access to secure resources.
Last updated
When sending your requests, you must include an OAuth 2 bearer authentication Access token in your request's Authorization HTTP header field of your request.
POST
https://live.betaapp.com/v1/auth/token
Use this endpoint to obtain an access token. After a successful request, save the token, as you might need it to communicate with our API in the future.
Content-type*
String
application/json
accept*
String
application/json
client_id*
String
The ID provided by Beta
client_secret*
String
Your secret
The response will return a new access token, a Refresh token and the number of remaining seconds that the token is valid for.
Each token is a JWT that contains an expiration time. We will return the same Access token to you each time you request one, until it expires. After an Access token expires, you must obtain new token from the authentication endpoint.
Request Example:
Response Example:
When calling our APIs, you must include the word "Bearer" before you include the token value.
POST
https://live.betaapp.com/v1/auth/revoke
This endpoint is used to revoke an access token from our cache. By revoking the token you can request a new one with the '/auth/token' endpoint
Content-Type*
String
application/json
accept*
String
application/json
client_id*
String
The ID provided by Beta
client_secret*
String
Your secret
If you send an expired Token to Beta, you will receive a 401 error, your integration must stop using this token and must request a new token to avoid receiving additional 401 errors.
Request Example:
Response Example: