Bappy API
stringstring
OAuth 2.0 authentication using the Client Credentials grant type (RFC 6749 §4.4).
Use your Client ID and Client Secret from OmaxTelecom Console to obtain an access token. The token has a limited lifetime — when it expires, simply request a new one.
Get Access Token
POST
https://api.omaxtelecom.com
/auth/token
Get Access Token
Obtain a Bearer access token using the OAuth 2.0 Client Credentials grant (RFC 6749 §4.4).
Setup
- Get your
client_idfrom OmaxTelecom Console - Get your
client_secretfrom OmaxTelecom Console
Request
Code
Response (200 OK)
Code
| Field | Type | Description |
|---|---|---|
access_token | string | Bearer token — include in Authorization header for all API calls |
expires_in | int | Token lifetime in seconds |
token_type | string | Always Bearer |
scope | string | Granted scopes |
Token Usage
Include the token in the Authorization header:
Code
Token Expiry
The client_credentials grant does not issue refresh tokens (RFC 6749 §4.4.3). When the token expires, request a new one by calling this endpoint again.
Errors
| HTTP | Error | Description |
|---|---|---|
| 401 | invalid_client | Client ID or Secret is incorrect |
| 400 | unsupported_grant_type | Wrong grant_type value |
| 400 | invalid_request | Missing required parameters |
Notes
- Use the returned
access_tokenin theAuthorization: Bearerheader for all API calls - Client ID and Secret are available at OmaxTelecom Console
Headers
Content-TypeAcceptGet Access Token › Responses
200
Successful response
No data returned