open.passengerflow.getManyShopsPassengerIndicatorData （Multi-store hourly data (corresponding to customer flow data of business platform) - [Compatible with PC4,PC5,PC6,PC8]）Sandbox debugging

Indicator description: 1. Inbound customer flow: the equipment bound under the main entrance and exit is counted; 2. In-store customer flow: the customer flow that passes through the store but does not enter the store; 3, outside the store customer flow: = into the store customer flow + over the store customer flow, that is, into the store does not enter the store are counted; 4, outbound customer flow: outbound customer flow (head and shoulder equipment can be counted, face equipment can not be counted); Special note: The use of face equipment statistics passenger flow, "analysis - single index" and "comparison - multi-store comparison" of the "time" dimension, the addition of each period and the page "summary" may appear inconsistent. Reason: Based on the principle of presenting actual passenger flow data, the summary data is weighted by day. Multiple occurrences in a day are counted as 1 person; data in each period is weighted by hour. Multiple occurrences in the same hour are counted as 1 person;

Interface description#

The environment	Interface method	Submission method	Do you need a signature	HTTP request routing
Formal environment	open.passengerflow.getManyShopsPassengerIndicatorData	POST	true	http://openapi.opretail.com/m.api

Common request parameters#

Parameters	Types of	Is required	The maximum length	Description	Example values
_aid	String	True	20	Open platform system number, fixed to S107	S107
_akey	String	True	20	Opretail open platform assigns developer keys to third parties	Obtained after certification of platform developer
_mt	String	True	100	Interface name	open.passengerflow.getManyShopsPassengerIndicatorData
_sm	String	True	100	Signature algorithm md5,sha1	md5
_requestMode	String	True	100	Request method post,get	POST
_version	String	True	100	Version number	v1
_timestamp	String	True	100	Timestamp	yyyyMMddHHmmss format
_sig	String	True	32	Signature token	Generated according to the signature algorithm, see the signature algorithm rules for details
_format	String	False	10	Format type	Currently only supports json by default

Business request parameters#

Parameters	Types of	Is required	The maximum length	Description	Example values
id	string	√	100	Store :"S_" + ID Organizational structure :"O_" + ID	O_1834
startTime	string	√	100	The start time	2020-08-19 00:00:00
endTime	string	√	100	The end of time	2020-08-19 23:59:59
starthour	int	×	11	The default 0	0
endhour	int	×	11	The default 24	24
timeType	int	×	11	Time type 1- Hour 2- Day 3- Week April - Month 5- Season 6- Year The default time latitude of the trend is 1	2

Common response parameters#

Parameters	Types of	The maximum length	Description	Example values
stat	JSON	-	Gateway status (specific parameters are described below :)	View
stat.cid	String	100	Http request identifier
stat.code	String	100	Gateway return code
stat.codename	String	100	Gateway return code name
stat.systime	String	Long	The current time of the interface call
result	String	100	Interface returns prompt information
data	JSON	-	Business information returned by the interface call (generally json format data, the specific data format will be defined in the business return parameters)	View

Business return parameters#

Parameter	Types of	Whether to return	Returns the maximum length	Description	Example values

Public return code#

Return code name	Return code	Return code description	Solution
SUCCESS	0	Call success
KEY_NOTNULL	1	_akey can not be empty	Input the _akey parameter when the interface is called
KEY_UNLAWFUL	2	_akey is illegal	key is illegal, input in the correct key
KEY_HAS_EXPIRED	3	_akey has expired	Please renew the service or contact the platform administrator
SIGN_METHOD_NOTNULL	4	_sm parameter cannot be empty	Input the _sm parameter when the interface is called
SIGN_TYPE_NOTEXIST	5	_sm type does not exist	Currently only supports md5, sha1
SIGN_NOTNULL	6	_sig parameter cannot be empty	Input the _sig parameter when the interface is called
SIGN_WRONG	7	Invalid signature, please check parameters and signature format	_sig value is generated according to the signature algorithm
METHOD_NOTNULL	8	_mt parameter cannot be empty	Input the _mt parameter when the interface is called
METHOD_NOTEXIST_CODE	9	The method name corresponding to _mt does not exist or is not registered in the service	Check if the method corresponding to _mt method name and _version version number is passed in error
REQUESTMODE_NOTNULL	10	_requestMode parameter cannot be empty	Input the _requestMode parameter when the interface is called
APPLICATIONID_NOTNULL	11	_aid parameter cannot be empty	Input the _aid parameter when the interface is called
APPLICATIONID_NOTSAME	12	_aid does not match the current key	_aid and _akey must correspond one-to-one
VERSION_NOTNULL	13	_version version number cannot be empty	Input the _version parameter when the interface is called
TIMESTAMP_NOTNULL	14	_timestamp timestamp cannot be empty	Input the _timestamp parameter when the interface is called
TIMESTAMP_FORMAT_ERROR	15	_timestamp timestamp formatting error	According to yyyyMMddHHmmss format
TIMESTAMP_OVERTIME	16	_timestamp has expired	_timestamp is regenerated every time the interface is called
FORMAT_TYPE_NOTEXIST	17	_format type does not exist	Currently only supports json (default), xml
API_CALL_REPEAT	-100	The interface is called repeatedly	Interface platform call exception
API_SYSTEM_CALL_ERROR	-500	API call failed, system exception occurred	Interface platform call exception
UNKNOWN_ERROR	-999	Open platform system exception	Reissue request

Business return code#

Return code name	Return code	Return code description