# Get Message Push Configuration

Interface should be called on the server side, seeHattori API。

# Interface Dxplaination

# Interface name

getCallBackConfig

# Functional description

This interface allows you to get the message push configuration. If you encounter problems during use, you canOpen Platform Service Provider ZonePosting exchanges.

# Calling mode

# HTTPS call


POST https://api.weixin.qq.com/tcb/getcallbackconfig?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

# Return parameters

attribute

type

Introductions

errcode

number

Error code

errmsg

string

Error message

data

object

data

attribute

type

Introductions

function_config

object

Cloud function configuration, if not filled, not updated

attribute

type

Introductions

enable

boolean

state

callbacks

array

Configuration item

attribute	type	Introductions
msgType	string	Message type
event	string	Type of event
env	string	Environment id
functionName	string	Cloud Function Name
enable	boolean	state

container_config

object

Cloud hosting configuration, if not filled, not updated

attribute	type	Introductions
enable	boolean	state
qbase_env	string	Environment id
qbase_container_path	string	Route
text_mode	number	Text format

# Call Example

Example Dxplaination: HTTPS requests

# Sample Request Data


POST https://api.weixin.qq.com/tcb/getcallbackconfig?access_token=ACCESS_TOKEN

# Return Data Example


{
    "errcode": 0,
    "errmsg": "ok",
    "data": {
        "function_config": {
            "enable": 初始值
            "callbacks": [
                {
                    "msgType": "event",
                    "event": "user_enter_tempsession",
                    "env": "test-env-6gni9ity244a6ea3",
                    "functionName": "callback",
                    "enable": false
                },
                {
                    "msgType": "image",
                    "event": "",
                    "env": "test-env-6gni9ity244a6ea3",
                    "functionName": "callback",
                    "enable": true
                }
            ]
        },
        "container_config": {
            "enable": true,
            "qbase_env": "test-env-6gni9ity244a6ea3",
            "qbase_container_path " : "/container-echo",
            "text_mode": 1
        }
    }
}

# Error code

Error code	Error code	Solutions
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
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 - 初始值 access_Token Middle, right. access_Token Detailed mechanism explaination of the
43002	require POST method	Need POST request