Authentication
Whenever your application requests one of the available features of our API, you must supply a token as a form of authentication. This token is generated through the endpoint described below.
OAuth2
We use industry-standard protocol OAuth 2.0 over HTTPS for authentication. It will allow the remote server to connect to our API endpoints. Unauthenticated requests will return an HTTP 401 response.
Request
POST
/oauth2/token
Content-Type: application/json
{
"access_token": "eyJraWQiOiI3V09TVjlRMUZLVnVkOFUxR0pMTFZhVEdrOTg2YVR5S0VUbzl6VXF6MGJZPSIsImFsZyI6IlJTMjU2In0.eyJzdWIiOiI2bnZ1NHUyZm5wYzdqYTByOGc2OWZqZzcxayIsInRva2VuX3VzZSI6ImFjY2VzcyIsInNjb3BlIjoiaHR0cHM6XC9cL2FwaS1xYS5saXF1aWRvLmNvbVwvdjFcL3BheW1lbnRzXC9jaGFyZ2VzXC9BTEwiLCJhdXRoX3RpbWUiOjE2NDI2NDUzNjQsImlzcyI6Imh0dHBzOlwvXC9jb2duaXRvLWlkcC5hcC1zb3V0aGVhc3QtMS5hbWF6b25hd3MuY29tXC9hcC1zb3V0aGVhc3QtMV9qc1NCVzlRYkwiLCJleHAiOjE2NDI2NDg5NjQsImlhdCI6MTY0MjY0NTM2NCwidmVyc2lvbiI6MiwianRpIjoiZTQ4ZWI3N2UtMzVhMC00NDE5LWJlYzgtOWVmNzcxOWU0NDY2IiwiY2xpZW50X2lkIjoiNm52dTR1MmZucGM3amEwcjhnNjlmamc3MWsifQ.MfhlJBRuHyP1pGIvmxffo5V5iNESq5hdPGhSaQY-kumU4lxQ6R42FcUNgU4JwhIvfYRP0K9oRH_f775bQdWbDsV2gcu3HL1irYYxtZSFlshulVf8rW7hVDMhCyB8oYEBODsMNu1Dnvrhle1MhHVLHweB-a7tbX7X5qtwJehVzNRiJkEBZ8D5FH_Ow32frkuZ9xbNnzCz68FRCmRVfszvN1eLMd0mh117Sf-apBO54mUN60aejH8iAegz0e-qm85mIxcjBP21GArK0J34R8mm0MnEEtjathh8YmICyo_Kxz77jMYnHxCsTQ3CkmWXePPa731Esi2am4l6AO1OklPp-w",
"expires_in": 3600,
"token_type": "Bearer"
}
HTTP Headers Details
Key | Value |
---|---|
Content-Type | application/x-www-form-urlencoded |
Request Body Details
Parameter | Required | Type | Description |
---|---|---|---|
client_id | String | The Id of the client | |
client_secret | String | The secret key of the client | |
grant_type | String | Must be "client_credentials" here |
Response Body Details
Parameter | Type | Description |
---|---|---|
access_token | String | access token |
expires_in | String | token will expire after {expires_in} seconds |
token_type | String | Must be "Bearer" here |