Authorization

Obtain an OAuth 2.0 access token using the client credentials flow. Generate client_id and client_secret from the credentials dashboard, then exchange them for a Bearer token.

Request

POST/api/v1/oauth/token

{{baseUrl}}/api/v1/oauth/token

Header

Header	Type	Description
Content-Type	string	application/json

Body Parameters

Parameter	Type	Description	Required
grant_type	string	Must be "client_credentials"	required
client_id	string	Client ID from the credentials dashboard	required
client_secret	string	Client secret — store server-side only	required

Response

200 OKSample dataExample response

{
  "success": true,
  "response_code": 200,
  "message": "Token generated successfully",
  "data": {
    "access_token": "exAmPlEtOkEn0123456789AbCdEfGhIjKlMnOpQrStUvWxYz",
    "token_type": "Bearer",
    "expires_in": 3600,
    "scope": "api"
  },
  "request_id": "550e8400-e29b-41d4-a716-446655440099"
}

Response Fields

Field	Type	Description
success	boolean	Whether the token request succeeded
response_code	number	Application response code (typically mirrors HTTP)
message	string	Human-readable status message
data.access_token	string	Token to send as Bearer on API calls
data.token_type	string	Always "Bearer"
data.expires_in	number	Token lifetime in seconds (typically 3600)
data.scope	string	Granted scope, usually "api"
request_id	string	UUID for support and audit trails

Set {{baseUrl}} to https://api.peleza.com (production) or https://sandbox.peleza.com (sandbox). Authenticated calls need a Bearer token from POST /api/v1/oauth/token.