# Short chains transition to longer information
Interface should be called on the server side, not in the front end (Weixin Mini Program, web pages, APP, etc.) directly called, specific reference interface call guide
Interface name: fetchShorten
Developers can convert long information not more than 4KB into short-chain key through GenShorten, and then restore short-chain key to long information through FetchShorten.
# 1. How to call
# HTTPS calls
POST https://api.weixin.qq.com/cgi-bin/shorten/fetch?access_token=ACCESS_TOKEN
# Cloud Calls
Call method: officialAccount.shorten.fetch
The input and exit parameters are the same as the HTTPS call, which can be called in the cloud call documentation
# Third party invocation
- Third Party Platform calls are not supported by this interface.
# 2. Request parameters
# Query parametersQuery String parameters
Parameter Name | type | Required to fill in | Introductions |
---|---|---|---|
access_token | string | yes | Interface invoke credentials, using access_token |
# Request BodyRequest Payload
Parameter Name | type | Required to fill in | Example | Introductions |
---|---|---|---|---|
short_key | string | yes | iTqRJFSEqk9RvPk | Shortkey |
# 3. Return Parameters
# Response Payload
Parameter Name | type | Introductions |
---|---|---|
errcode | number | Error code |
errmsg | string | Error message |
long_data | string | Long information |
create_time | timestamp | Created timestamp |
expire_seconds | number | Number of remaining expiration seconds |
# 4. Note
There are no special considerations for this interface
# 5. Code examples
Example Requests
{
"short_key": "iTqRJFSEqk9RvPk"
}
Return an example
{
"errcode": 0,
"errmsg": "ok",
"long_data": "loooooong data",
"create_time": 1611047541,
"expire_seconds": 86300
}
# 6. Error code
The following is a list of error codes for this interface, other error codes can refer to General error codes
Error code | Error Description | Solutions |
---|---|---|
-1 | system error | The system is busy, so the developer is asked to try again in a few minutes. |
44002 | empty post data | The POST number is empty. The post request body parameter cannot be empty. |
47001 | data format error | Error parsing JSON / XML content; Missing parameters in post data; The review was amended and a second attempt was made. |
47003 | argument invalid! | Template parameter is inaccurate, may be empty or does not meet the rules, errmsg will indicate which field is wrong |
9410012 | This page does not exist / is not available. |
# 7. Scope of application
The interface has not yet clarified the types of account numbers that can be invoked, or determined whether they can be invoking based on the invoking reference in the business, provided that the actual call is already made.