English
Legacy Parameter Passing Method Documentation
About 201 wordsLess than 1 minute
2026-01-19
Obtaining AccessToken and corpId via API Call
Request Specification
Method: POST + application/json
Endpoint: https://${cloud-domain}/cgi/corpAccessToken/get/V2?thirdTraceId=${Random String}
Request Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
| appId | String | Yes | AppId (Enterprise Application ID), obtained as described in Quick Start 4.3 |
| appSecret | String | Yes | APPSecret (Enterprise Application Credential Key), obtained as described in Quick Start 4.3 |
| permanentCode | String | Yes | Permanent authorization code, obtained as described in Quick Start 4.3 |
Request Example
{
"appId":"APPID",
"appSecret":"APPSECRET",
"permanentCode":"PERMANETCODE"
}Response Parameters
| Parameter | Required | Description |
|---|---|---|
| errorCode | Yes | Return code |
| errorMessage | Yes | Text description of the return code |
| corpAccessToken | Yes | Enterprise application access token for company verification |
| corpId | Yes | Company account issued by the open platform |
| expiresIn | Yes | Expiration time of the enterprise access token in seconds (0~7200). When requested between 0-6600 seconds, the same corpAccessToken will be returned. When requested between 6600-7200 seconds, a new token will be issued. Token renewal should be requested during this period. |
Calling Specific APIs
No request headers are required. Common parameters should be included in the request body.
Request Example
{
"corpAccessToken": "{corpAccessToken}",
"currentOpenUserId": "{currentOpenUserId}",
"corpId": "{corpId}",
"data": {}
}