# Get Tencent Cloud API call certificate
Interface should be called on the server side, seeHattori API。
# Interface Dxplaination
# Interface name
GetCloudToken
# Functional description
- Through this interface you can get Tencent cloud API call certificate,Tencent Cloud Available API general overview。 初始值 If you encounter problems during use, you canOpen Platform Service Provider ZonePosting exchanges.
# Note
1, the interface has a frequency limit: 10 times per hour.
- Tencent Cloud API Call Dxplaination
- this API Certificates in exchange can only be used forTencent Cloud Available API OverviewThe API listed in.
- Reference to the use of calling credentialsTencent Cloud Public Parameters
# Calling mode
# HTTPS call
POST https://api.weixin.qq.com/tcb/getqcloudtoken?access_token=ACCESS_TOKEN
# Third Party Invocation
The calling method and parameters are the same as HTTPS, only the calling token is different
The permission set id to which this interface belongs is: 49, 64
After the service provider has been authorized with one of the permission sets, it can do so by usingauthorizer_access_TokenCalling on behalf of the merchant
# Request parameters
| attribute | type | Required | Introductions |
|---|---|---|---|
| access_Token | string | yes | Interface invokes the certificate, which is URL Parameters, non Body Parameters. useauthorizer_access_Token |
| lifespan | number | yes | Duration (in seconds, max. 7200) |
# Return parameters
| attribute | type | Introductions |
|---|---|---|
| errcode | number | Error code |
| errmsg | string | Error message |
| secretid | string | secretid |
| secretkey | string | secretkey |
| Token | string | Token |
| expired_time | number | Expiration timestamp |
# Call Example
Example Dxplaination: HTTPS requests
# Sample Request Data
{
"lifespan" : 7200
}
# Return Data Example
{
"errcode": 0,
"errmsg": "ok",
"secretid": "SECRETID",
"secretkey": "SECRETKEY",
"token": "TOKEN",
"expired_time": 1557310488
}
# Error code
| Error code | Error code | Solutions |
|---|---|---|
| 40001 | invalid credential access_Token isinvalid or not latest | Obtain access_Token time AppSecret Error, or access_Token Invalid. Please take the developer more seriously. AppSecret Of the correctness, or to see if you are working for the appropriate Official Account message template Call interface |
| 0 | ok | ok |
| -1 | system error | The system is busy, please wait for the developer to try again |
| -1000 | system error | System error |
| 40014 | invalid access_Token | Illegal access_Token Please take the developer seriously. access_Token Of the validity (such as whether it is expired), or to see if you are working for the appropriate Official Account message template Call interface |
| 40097 | invalid args | Parameter error |
| 40101 | missing parameter | Missing required parameters |
| 41001 | access_Token missing | lack access_Token parameter |
| 42001 | access_Token expired | access_Token Timeout, please check access_Token Of the validity period, please refer to the Basic Support - Obtain access_Token Middle, right. access_Token Detailed mechanism explaination of the |
| 43002 | require POST method | Need POST request |
| 44002 | empty post data | POST The packet is empty. |
| 45009 | reach max api daily quota limit | The call exceeded the day-level frequency limit. Callable clear_The quota interface restores the invocation quota. |
| 47001 | data format error | analysis JSON/XML Content errorpost Missing parameters in the dataCheck for corrections and try again. |
| 85088 | no qbase privilege | The app is not open for cloud development |