The message service is an active push service launched by the Xport developer platform to improve efficiency, and the push content is currently only open to order-related messages. Based on this push service, the application no longer needs polling API to obtain distribution data, but only needs the open platform to actively push business content to the developer when the business data corresponding to the message changes, and the developer only needs to subscribe to the message in advance and analyze the message content. It should be noted that since the order of messages cannot be guaranteed, some messages need to be synchronized with the OpenAPI query interface. Message access can effectively reduce API call frequency and reduce system pressure.
Location: Open Platform Application Console - Messaging ServiceSteps: Developers can configure a callback URL on the open platform to receive message requestsLogin to the Xport Open platform as a developer; Select the console; Select the message service; Enter the callback address and select Verify. If the HTTP 200 status code is returned, the verification is successful. Select Save.
messageType: indicates the message type messageBody: indicates the message body messagePlatform: Message channel 0-Taobao platform 1-1688 platform timestamp: Message push time
Description: Developers need to provide a message receiving channel, receiving push in the form of HTTPS POST requests.To use the message service, you need to prepare a callback interface for receiving messages. Perform the following operations:Use the HTTPS callback address. After receiving the message, return the HTTP 200 status code to confirm the message signing. The timeout period is 1000MS.
If the message fails, it will be pushed again half an hour later, with a maximum of 5 retries. If the system is interrupted for more than five times, obtain data again through related query interfaces.
Description: Data will be transmitted in plain text. For security reasons, the open platform will perform summary signature processing on the message body, and the signature result will be placed in the Authorization field of the POST request header. The signature algorithm is as follows:#Request signature parametersBase = "{messageBody}"Secret = "{AccessSecret}"#Signature algorithmHMAC-SHA256#Generate signatureAuthorization = HEX_ENCODE(HMAC-SHA256(Base, Secret));Java signature code reference：
After receiving the message, verify the signature to prevent external attacks, and do not convert or modify the original message body when signing! Otherwise, signature matching will be inconsistent. Note: messageBody is a string. Because the interface response time is limited (within 1000ms), the message can be stored in the asynchronous queue for service processing.
