Get Access Token
- 03 Mar 2023
- 1 読む分
- 印刷する
- 闇光
- PDF
Get Access Token
- 更新日 03 Mar 2023
- 1 読む分
- 印刷する
- 闇光
- PDF
The content is currently unavailable in Ja - 日本語. You are viewing the default English version.
記事の要約
この要約は役に立ちましたか?
ご意見ありがとうございます
To get the access token, a user must use the generated Client Id and Client Secret.
- Click Get Access Token in the API Integration section from the left navigation panel.
Get Access Token
- You can also navigate to Get Access Token from the bottom right corner of the Generate Credentials page.
Generate Credentials
- The Get Access Token page appears, and the POST URL is generated by default.
Get Access Token – POST URL
- In the Request Body section, click on Example to view the attributes required to get the access token:
Example | Description |
---|---|
client_id | This is a mandatory field; the information is generated from the Generate Credentials page. |
client_secret | This is a mandatory field; the information is generated from the Generate Credentials page. |
All other parameters are dynamic in nature, may or may not be applicable for a business entity.
Get Access Token - Request Body Example
- To view the properties of the attributes displayed in Example section, click on Schema.
Get Access Token -Request Body Schema
The default request body is JSON format, which can be changed to data format if required.
- In the Responses section, you can view the following response codes applicable (both success & error):
Responses | Description |
---|---|
200 | Successfully done |
400 | Current valid scope is “DLAT access Webhooks” |
401 | Invalid token |
404 | Client id not found |
412 | Validation errors/Invalid Arguments. |
503 | Something went wrong. |
Get Access Token -Responses
- By default, the response code 200 is selected.
- In the Response Body, you will get the appropriate response (success or error) when selecting a particular response code.
この記事は役に立ちましたか?