# Set Login Configuration
Interface should be called on the server side, seeHattori API。
# Interface Dxplaination
# Interface name
weDataSetLoginConfig
# Functional description
Setting Up Service Provider Login Configuration
# Note
Login configuration is divided into PC side and Mini Program side, according to different access mode need to configure the corresponding information.
# PC end
The PC side login needs to configure the reverse lookup address to query the login state of the user to access the service provider system, so the service provider needs to provide the reverse lookup interface, details can be seen file->3. Access Process ->Step 3 ->PC End ->Login State Back Check
# Mini Program end
- The Mini Program side login needs to configure the associated Mini Program with the third-party platform account, and the jump request is initiated by the associated Mini Program, and the maximum number of associated Mini Program is 5.
- Note that the associated Mini Program here refers to the Mini Program that the service provider uses to initiate the jump we analysis, not the Mini Program of the merchant.
- After the configuration is completed, the Mini Program side of the third party platform can transfer the We analysis Mini Program to the form of a half screen by calling the "half-screen Mini Program." Details can be seen file->3. Access Process ->Step 3 ->Mini Program end
# Calling mode
# HTTPS call
初始值 https://api.weixin.qq.com/wedata/wedata_set_login_config?access_token=ACCESS_TOKEN
# Request parameters
| attribute | type | Required | Introductions |
|---|---|---|---|
| access_Token | string | yes | Interface invokes the certificate, which is URL Parameters, non 初始值 Parameters. usecomponent_access_Token |
| set_type | number | yes | 1: Configure reverse lookup address 2: Configure the associated appid |
| recheck_url | string | no | Address, set_type = 1, if empty means delete |
| associate_appid | array | no | Associate appid,set_Effective when type = 2, if empty, delete |
# Return parameters
| attribute | type | Introductions |
|---|---|---|
| errcode | number | Error code |
| errmsg | string | Error message |
# Other Notes
# Login State Back Check
describe: This interface is provided by the service provider itself, and it is based on the login state of the user login in the service provider's system to check the user's UID and expiration time.
address： ***(The server provides the HTTP request address, but the request parameters and return parameters need to follow the documentation.)
Request method：POST application/json
Request parameters：
| ParameterName | type | Is it necessary to | Remarks |
|---|---|---|---|
| user_session | string | yes | Server session, the session in which the user accesses the server's system |
Return parameters：
| ParameterName | type | Is it necessary to | Remarks |
|---|---|---|---|
| ret | number | yes | Return code |
| err_msg | string | yes | Return Information |
| uid | string | yes | The unique identification of the user in the service provider system, which can be a mobile number, email, employee ID, etc. |
| expire_at | number | yes | Expiration time (unix timestamp in seconds) |
# Call Example
Example Dxplaination: Configure reverse lookup address
# Sample Request Data
{
"set_type": 1,
"recheck_url": "xxxxxxxxx"
}
# Return Data Example
{
"errcode": 0,
"errmsg": "OK",
}
Example Dxplaination: Configure associative appid
# Sample Request Data
{
"set_type": 2,
"associate_appid": ["xxxxxxxxx"]
}
# Return Data Example
{
"errcode": 0,
"errmsg": "OK",
}
# Error code
| Error code | Error code | Solutions |
|---|---|---|
| -1 | system error | The system is busy, please wait for the developer to try again |
| 9900004 | Request parameter error | Please double check the request parameter format |