Sign in
latestOpenAPI 3.0.1Proprietary2026-08-1844131294.9 KB

59cd6443fdbf

Partner Token

OAuth 2.0 Token Endpoint

Implements RFC 6749 Section 4.4.2 - Access Token Request using Client Credentials flow.

This endpoint accepts both JSON and form-urlencoded content types.

Security considerations:

  • Uses HTTPS in production (enforced by infrastructure)
  • Validates client credentials using Argon2 password hashing
  • Generates cryptographically secure opaque tokens

Grant Type:

  • Only client_credentials grant type is supported

Authentication:

  • This endpoint does NOT require a bearer token
  • Authentication is performed using client_id and client_secret in the request body
post/v1/client/token

Request body

grant_type'client_credentials' required

OAuth 2.0 grant type (must be "client_credentials")

client_idstring required

Client ID provided by Multiplier

client_secretstring password required

Client secret provided by Multiplier

scopestring

Optional scope (currently not supported)

Example request

{
  "grant_type": "client_credentials",
  "client_id": "partner_abc123",
  "client_secret": "secret_xyz789"
}

Response

Token issued successfully

access_tokenstring required

The access token to use for authenticated requests

token_type'Bearer' required

Token type (always "Bearer")

expires_ininteger required

Token expiration time in seconds

Example response

{
  "access_token": "tok_abc123def456ghi789jkl012mno345pqrst",
  "token_type": "Bearer",
  "expires_in": 3600
}