万店掌 开放平台 Get passenger flow indicator data

open.shopweb.passengerFlow.getPassengerIndicatorData (Get passenger flow indicator data)Sandbox debugging

Indicator description: 1. Inbound passenger flow: count the equipment bound to the main entrance; 2. In-store passenger flow: passenger flow through the store but not in the store; 3. Out-of-store passenger flow: = in-store passenger flow + in-store passenger flow, that is, enter Stores that do not enter the store are counted; 4. Out-of-store passenger flow: Out-of-store passenger flow (head and shoulder equipment can be counted, face equipment cannot be counted); Special note: When using facial equipment to count passenger flow, "Analysis-Individual Index" and "Comparison" -Under the "time" dimension of "multi-store comparison", there may be inconsistencies between the sum of each time period and the page "summary". Reason: Based on the principle of presenting actual passenger flow data, the aggregated data is deduplicated by day, and multiple occurrences within a day are counted as 1 person, and the data for each period is deduplicated by the hour, and multiple occurrences within the same hour are counted as 1 person, and within multiple hours Occurs once in each period.

Interface description#

The environmentInterface methodSubmission methodDo you need a signatureHTTP request routing
Formal environmentopen.shopweb.passengerFlow.getPassengerIndicatorDataPOSTtruehttp://openapi.opretail.com/m.api

Common request parameters#

ParametersTypes ofIs requiredThe maximum lengthDescriptionExample values
_aidStringTrue20Open platform system number, fixed to S107S107
_akeyStringTrue20Opretail open platform assigns developer keys to third partiesObtained after certification of platform developer
_mtStringTrue100Interface nameopen.shopweb.passengerFlow.getPassengerIndicatorData
_smStringTrue100Signature algorithm md5,sha1md5
_requestModeStringTrue100Request method post,getPOST
_versionStringTrue100Version numberv1
_timestampStringTrue100TimestampyyyyMMddHHmmss format
_sigStringTrue32Signature tokenGenerated according to the signature algorithm, see the signature algorithm rules for details
_formatStringFalse10Format typeCurrently only supports json by default

Business request parameters#

ParametersTypes ofIs requiredThe maximum lengthDescriptionExample values
depId
int11Store id 17465
startTime
string100Starting time demo: 2020-06-01 00:00:002020-06-01 00:00:00
endTime
string100End Time demo: 2020-06-17 23:59:592020-06-17 23:59:59

Common response parameters#

ParametersTypes ofThe maximum lengthDescriptionExample values
statJSON-Gateway status (specific parameters are described below :)View
stat.cidString100Http request identifier
stat.codeString100Gateway return code
stat.codenameString100Gateway return code name
stat.systimeStringLongThe current time of the interface call
resultString100Interface returns prompt information
dataJSON-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#

ParameterTypes ofWhether to returnReturns the maximum lengthDescriptionExample values
passengerFlow
int×11Walk-in Count: Count the equipment bound under the main entrance and exit;1674
outsidePassengerFlow
int×11Outside passenger flow = Walk-in Count +Passing Store Count, that is, not only count walk in, but also count those who passing the store but not enter the store.168
inShopRate
float×10Walk-in Rate = Walk-in Count/Outside passenger flow*100% =Walk-in Count/(Walk-in Count +Passing Store Count)*100% (the overall enterprise Walk-in Rate does not include the stores that are not bound with outside people counting device)0.00
outFlowCount
int×11Walk-out Count: Walk-out Count(head and shoulder equipment can be counted, facial equipment cannot be counted)0
dressingRate
float×10Fitting Rate = Customes flow in the fitting room/ Walk-in Count*100%, that is, the proportion of in-store customers who go for fitting;0.00
passPassengerFlow
int×11Passing Store Count = passenger flow passing the store but not entering the store;10

Public return code#

Return code nameReturn codeReturn code descriptionSolution
SUCCESS0Call success
KEY_NOTNULL1_akey can not be emptyInput the _akey parameter when the interface is called
KEY_UNLAWFUL2_akey is illegalkey is illegal, input in the correct key
KEY_HAS_EXPIRED3_akey has expiredPlease renew the service or contact the platform administrator
SIGN_METHOD_NOTNULL4_sm parameter cannot be emptyInput the _sm parameter when the interface is called
SIGN_TYPE_NOTEXIST5_sm type does not existCurrently only supports md5, sha1
SIGN_NOTNULL6_sig parameter cannot be emptyInput the _sig parameter when the interface is called
SIGN_WRONG7Invalid signature, please check parameters and signature format_sig value is generated according to the signature algorithm
METHOD_NOTNULL8_mt parameter cannot be emptyInput the _mt parameter when the interface is called
METHOD_NOTEXIST_CODE9The method name corresponding to _mt does not exist or is not registered in the serviceCheck if the method corresponding to _mt method name and _version version number is passed in error
REQUESTMODE_NOTNULL10_requestMode parameter cannot be emptyInput the _requestMode parameter when the interface is called
APPLICATIONID_NOTNULL11_aid parameter cannot be emptyInput the _aid parameter when the interface is called
APPLICATIONID_NOTSAME12_aid does not match the current key_aid and _akey must correspond one-to-one
VERSION_NOTNULL13_version version number cannot be emptyInput the _version parameter when the interface is called
TIMESTAMP_NOTNULL14_timestamp timestamp cannot be emptyInput the _timestamp parameter when the interface is called
TIMESTAMP_FORMAT_ERROR15_timestamp timestamp formatting errorAccording to yyyyMMddHHmmss format
TIMESTAMP_OVERTIME16_timestamp has expired_timestamp is regenerated every time the interface is called
FORMAT_TYPE_NOTEXIST17_format type does not existCurrently only supports json (default), xml
API_CALL_REPEAT-100The interface is called repeatedlyInterface platform call exception
API_SYSTEM_CALL_ERROR-500API call failed, system exception occurredInterface platform call exception
UNKNOWN_ERROR-999Open platform system exceptionReissue request

Business return code#

Return code nameReturn codeReturn code description