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. Token lifetime is configured server-side (TOKEN_TTL_SECONDS; currently 360 seconds / 6 minutes).
Request
POST/api/v1/oauth/token
{{baseUrl}}/api/v1/oauth/tokenHeader
Body Parameters
Sample request & response
Sample request body for Sample request & response:
Sample dataSample request body
{
"grant_type": "client_credentials",
"client_id": "pel_XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX",
"client_secret": "skl_XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX"
}Sample response for Sample request & response:
200 OKSample dataSample response
{
"success": true,
"response_code": 200,
"message": "Token generated successfully",
"data": {
"access_token": "exAmPlEtOkEn0123456789AbCdEfGhIjKlMnOpQrStUvWxYz ......",
"token_type": "Bearer",
"expires_in": 360
},
"request_id": "550e8400-e29b-41d4-a716-446655440099"
}Response Fields
Error codes
Standard Peleza HTTP / response_code values (same across all API calls). Validation message text is endpoint-specific. Full reference: Error Codes.
401 β invalid credentials
401Sample data401 β invalid credentials
{
"success": false,
"response_code": 401,
"message": "Invalid client credentials",
"data": null,
"request_id": "550e8400-e29b-41d4-a716-446655440020"
}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.
