# Manage WeChat token permissions
Interface should be called on the server side, seeHattori API。
# Interface Dxplaination
# Interface name
setCloudAccessToken
# Functional description
This interface enables you to turn cloudbase on or off_access_If you encounter problems during the use of the token, you can use theOpen Platform Service Provider ZonePosting exchanges.
# Note
- This permission is turned on by default. Call this interface to turn off cloudbase_access_Token permissions, the account will not be able to use cloudbase_access_token。 On-demand configuration allows the use of the open interface of WeChat tokens, unconfigured interfaces cannot use cloud calls.
- If it is batch generation cloud development, use component_access_Token
- If it is a normal generation cloud development, use the authorizer_access_token。
# Calling mode
# HTTPS call
POST https://api.weixin.qq.com/tcb/usecloudaccesstoken?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. usecomponent_access_TokenOr useauthorizer_access_Token |
action | string | yes | Optional get or set |
open | boolean | yes | True means open, false means closed. Global configuration, required when action = set. |
api_whitelist | array | yes | Api whitelist, required when action = set. |
env | string | yes | Environment id , White List Configuration for Environment Dimension |
version | number | yes | Version number, required when action = set |
# Return parameters
attribute | type | Introductions |
---|---|---|
errcode | number | Error code |
errmsg | string | Error message |
open | boolean | open/Closed, returned when action = get |
api_whitelist | array | Api whitelist, returned when action = get |
version | number | Version number, returned when action = get |
# Call Example
Example Dxplaination: Get Example
# Sample Request Data
{
"action": "get",
"env": "myttest-8gu57so0bd9f9e8a"
}
# Return Data Example
{
"errcode": 0,
"errmsg": "ok",
"open": true,
"api_Whitelist: [
"/*"
],
"version": 2
}
Example Dxplaination: set example
# Sample Request Data
{
"action": "set",
"open": true,
"env": "myttest-8gu57so0bd9f9e8a"
"api_Whitelist: ["/*"],
"version": 6
}
# Return Data Example
{
"errcode": 0,
"errmsg": "ok",
"open": true
}
# Error code
Error code | Error code | Solutions |
---|---|---|
-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 Of the packet is empty. The post request body parameter cannot be null. |
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 |