# Get graphic forwarding timed data
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 English name: getusersharehour
This interface is used to obtain graph forwarding timed data
# 1. How to call
# HTTPS calls
POST https://api.weixin.qq.com/datacube/getusersharehour?access_token=ACCESS_TOKEN
# Cloud Calls
Call method: officialAccount.datacube.getUserShareHour
The input and exit parameters are the same as the HTTPS call, which can be called in the cloud call documentation
# Third party invocation
This interface supports Third Party Platform generation business call.
The permission set id to which the interface belongs is: 7
When a service provider is authorized by one of the permissions set, it can call on behalf of the merchant by using authorizer_access_token , which can be viewed in the third-party call documentation.
# 2. Request parameters
# Query parametersQuery String parameters
Parameter Name | type | Required to fill in | Introductions |
---|---|---|---|
access_token | string | yes | Interface invocation credentials, using access_token , authorizer_access_token |
# Request BodyRequest Payload
Parameter Name | type | Required to fill in | Example | Introductions |
---|---|---|---|---|
begin_date | string | yes | 2023-01-01 | Start date (YYYY-MM-DD) |
end_date | string | yes | 2023-01-01 | End Date (maximum value is yesterday) |
# 3. Return Parameters
# Response Payload
Parameter Name | type | Introductions |
---|---|---|
list | objarray | List of data |
# Res.list(Array)Object Payload
List of data
Parameter Name | type | Introductions |
---|---|---|
ref_date | string | Date of data, between begin_date and end_date |
ref_hour | number | Data Hour |
share_user | number | Number of people shared |
share_count | number | Number of times shared |
share_scene | number | The codes 1, 2, and 255 represent "friends sharing," "WeChat Moments," and "other," respectively. |
# 4. Note
There are no special considerations for this interface
# 5. Code examples
Example Requests
{
"begin_date": "2014-12-08",
"end_date": "2014-12-08"
}
Return an example
{
"list": [
{
"ref_date": "2014-12-07",
"ref_hour": 1200,
"share_scene": 1,
"share_count": 72,
"share_user": 4
}
]
}
# 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. |
40001 | invalid credential access_token isinvalid or not latest | AppSecret error while getting access_token, or access_token is invalid.Developers should check that AppSecret is correct, or that they are calling interfaces for the appropriate Official Account |
# 7. Scope of application
Official Account | Service Account |
---|---|
Certification only | Certification only |
- Authentication only: means that only authenticated accounts are allowed to be invoked by the enterprise entity, and accounts that are not authenticated or do not support authentication cannot be invoked.
- Other account types that are not expressly stated may not be called on this interface without special instructions;