Inquiry API
Logistics query API provides real -time query logistics trajectory services. Users provide the transport order number and courier companies to query the latest logistics trajectory of the current moment.
Application scenario
(1) The user of e -commerce website users call this API display logistics information details when “My Order” is opened.
(2) Logistics system in the background of e -commerce administration. Customer service query the signing status of all the transportation orders before the reconciliation, and track the problem.
(3) The number of daily calls does not exceed 3,000 times. If this limit is exceeded, please dock
Logistics tracking API
。
(4) The logistics status tracking of the whole process, instant query unlimited times, please dock
Monitor API on the way。
(2) Logistics system in the background of e -commerce administration. Customer service query the signing status of all the transportation orders before the reconciliation, and track the problem.
(3) The number of daily calls does not exceed 3,000 times. If this limit is exceeded, please dock
Logistics tracking API
。
(4) The logistics status tracking of the whole process, instant query unlimited times, please dock
Monitor API on the way。
function description
Use process
API parameters
1. Interface description/description
(1) Inquiry interface support according to the transport number number (single query).
(2) The interface needs to specify the coding company coding of the courier single number, and the format is wrong or the encoding error will return the failure information.
, such as: EMS logistics single number should choose express company encoding (EMS)
View express company coding
(3) The logistics tracking information returned is arranged according to the occurrence of the occurrence of the time.
(4) Interface instruction 1002.
(5) The message receiving method supported by the interface isHTTP POST, the encoding format of the request method (UTF-8):“application/x-www-form-urlencoded;charset=utf-8”。
(6) Interface Address: API Address: http://api.kdniao.cc/ebusiness/ebusInssederhandle.aspx
(2) The interface needs to specify the coding company coding of the courier single number, and the format is wrong or the encoding error will return the failure information.
, such as: EMS logistics single number should choose express company encoding (EMS)
View express company coding
(3) The logistics tracking information returned is arranged according to the occurrence of the occurrence of the time.
(4) Interface instruction 1002.
(5) The message receiving method supported by the interface isHTTP POST, the encoding format of the request method (UTF-8):“application/x-www-form-urlencoded;charset=utf-8”。
(6) Interface Address: API Address: http://api.kdniao.cc/ebusiness/ebusInssederhandle.aspx
Request system -level parameter description:
Parameter name | Instructions | Must require | |
---|---|---|---|
RequestData | String | The request content needs to be encoded in URL (UTF-8). The request content is JSON format, which must be consistent with DataType. | R |
EBusinessID | String | Merchant ID, please check on my service page. | R |
RequestType | String | Request instruction Type: 1002 | R |
DataSign | String | Data content signature: Md5 encryption (request content (uncoded)+appKey), then use 64 encoding, and finally coded URL (UTF-8). For a detailed process, please check Demo. | R |
DataType | String | request, return data type: 2-json; | O |
Remarks:R-required, O-optional (optional), C-packet can be optional under certain conditions (Conditional)
2, interface parameters
Request content field definition:
Parameter name | type | Instructions | Must require |
---|---|---|---|
OrderCode | String | Order number | O |
ShipperCode | String | Express company encoding | R |
LogisticCode | String | Logistics single number | R |
Back parameter definition:
Parameter name | type | Instructions | Must require |
---|---|---|---|
EBusinessID | String | User ID | R |
OrderCode | String | Order number | O |
ShipperCode | String | Express company encoding | R |
LogisticCode | String | Logistics operation order number | O |
Success | Bool | Is it successful? | R |
Reason | String | Failure reason | O |
State | String | Logistics status: 2-On the way, 3-sign, 4-Question parts | R |
Traces | |||
AcceptTime | String | time | R |
AcceptStation | String | Description | R |
Remark | String | Remarks | O |
3. Example
Request Example JSON
{
"OrderCode": "",
"ShipperCode": "SF",
"LogisticCode": "118650888018"
}
Return to example JSON
No logistics trajectory
{{
"Ebusinessid": "1109259",
"Traces": [],,
"OrderCode": "",
"Shippercode": "sf", "sf",
"LogisticCode": "118461988807",
"Success": False,
"Reason": null
}
With a logistics trajectory
{{
"Ebusinessid": "1109259",
"OrderCode": "",
"Shippercode": "sf", "sf",
"LogisticCode": "118461988807",
"Success": true,
"State": 3,
"Reason": null,
"Traces": [[
{{
"Accepttime": "2014/06/25 08:05:37",,
"AcceptStation": "Dating .. (Displayer: Deng Yuli, Telephone: 18718866310) [Shenzhen]"
"Remark": null
},
{{
"Accepttime": "2014/06/25 04:01:28",,
"AcceptStation": "Express is in Shenzhen distribution center, ready to be sent to the next stop Shenzhen [Shenzhen]", "Shenzhen [Shenzhen]", "
"Remark": null
},
{{
"Accepttime": "2014/06/25 01:41:06",,
"AcceptStation": "Express is in Shenzhen Distribution Center [Shenzhen]",
"Remark": null
},
{{
"Accepttime": "2014/06/24 20:18:58",
"AcceptStation": "Received [Shenzhen]",
"Remark": null
},
{{
"Accepttime": "2014/06/24 20:55:28",,
"AcceptStation": "Express is in Shenzhen, ready to be sent to the next stop Shenzhen distribution center [Shenzhen]",, "Shenzhen]", "
"Remark": null
},
{{
"Accepttime": "2014/06/25 10:23:03",,
"Acceptstation": "The part of the parts has been signed [Shenzhen]",
"Remark": null
},
{{
"Accepttime": "2014/06/25 10:23:03",,
"AcceptStation": "Signing the receiver: Has been signed [Shenzhen]",
"Remark": null
}
]
}
access process
For details, please click to enter the courier bird official website -instant query APIhttp://www.kdniao.com/api-track