When an ordinary WeChat user sends a message to a public account, the WeChat server will send the XML packet of the POST message to the server address URL configured by the developer in the WeChat public account management background.
The push XML packet structure of common message types is as follows.
Text message
<xml>
<ToUserName><![CDATA[Developer WeChat ID]]></ToUserName>
<FromUserName><![CDATA[Sendor OpenID]]></FromUserName>
<CreateTime>Message creation time (integer)</CreateTime>
<MsgType><![CDATA[text]]></MsgType>
<Content><![CDATA[Text Message Content]]></Content>
<MsgId>Message id, 64-bit integer</MsgId>
</xml>Picture message
<xml>
<ToUserName><![CDATA[Developer WeChat ID]]></ToUserName>
<FromUserName><![CDATA[Sendor OpenID]]></FromUserName>
<CreateTime>Message creation time (integer)</CreateTime>
<MsgType><![CDATA[image]]></MsgType>
<PicUrl><![CDATA[Pic link (generated by the system)]]></PicUrl>
<MediaId><![CDATA[Image Message Media ID, you can call the multimedia file download interface to pull data]]></MediaId>
<MsgId>Message id, 64-bit integer</MsgId>
</xml>Voice message
For public accounts that enable voice recognition, every time a user sends a voice to the public account, WeChat will add a Recongnition field to the pushed voice message XML packet (Note: Due to client cache, the developer enables or turns off the voice recognition function, which will take effect immediately for new followers, and it will take effect 24 hours for users who have followed. Developers can follow this account again for testing).
<xml>
<ToUserName><![CDATA[Developer WeChat ID]]></ToUserName>
<FromUserName><![CDATA[Sendor OpenID]]></FromUserName>
<CreateTime>Message creation time (integer)</CreateTime>
<MsgType><![CDATA[voice]]></MsgType>
<MediaId><![CDATA[Image Message Media ID, you can call the multimedia file download interface to pull data]]></MediaId>
<Format><![CDATA[voice formats, such as amr, speex, etc.]]></Format>
<Recognition><![CDATA[Only when voice recognition is enabled, voice recognition results, UTF8 encoding]]></Recognition>
<MsgId>Message id, 64-bit integer</MsgId>
</xml>Video or short video message
<xml>
<ToUserName><![CDATA[Developer WeChat ID]]></ToUserName>
<FromUserName><![CDATA[Sendor OpenID]]></FromUserName>
<CreateTime>Message creation time (integer)</CreateTime>
<MsgType><![CDATA[vieo or shortvideo]]></MsgType>
<MediaId><![CDATA[Image Message Media ID, you can call the multimedia file download interface to pull data]]></MediaId>
<ThumbMediaId><![CDATA[Media id of video message thumbnail, you can call the multimedia file download interface to pull data]]></ThumbMediaId>
<MsgId>Message id, 64-bit integer</MsgId>
</xml>Geographic location message
<xml>
<ToUserName><![CDATA[Developer WeChat ID]]></ToUserName>
<FromUserName><![CDATA[Sendor OpenID]]></FromUserName>
<CreateTime>Message creation time (integer)</CreateTime>
<MsgType><![CDATA[location]]></MsgType>
<Location_X>Geographical Location Latitude</Location_X>
<Location_Y>Geographical Location Longitude</Location_Y>
<Scale>Map Scale</Scale>
<Label><![CDATA[Geographical Location Information]]></Label>
<MsgId>Message id, 64-bit integer</MsgId>
</xml>Link message
<xml>
<ToUserName><![CDATA[Developer WeChat ID]]></ToUserName>
<FromUserName><![CDATA[Sendor OpenID]]></FromUserName>
<CreateTime>Message creation time (integer)</CreateTime>
<MsgType><![CDATA[link]]></MsgType>
<Title><![CDATA[Message Title]]></Title>
<Description><![CDATA[Message Description]]></Description>
<Url><![CDATA[Message Link]]></Url>
<MsgId>Message id, 64-bit integer</MsgId>
</xml>
Please note:
1. Regarding the retry message scheduling, it is recommended to use msgid to scheduling.
2. If the WeChat server fails to receive a response within five seconds, it will disconnect and initiate a request again, and try three times in total. If the server cannot guarantee that it will process and reply within five seconds, it can directly reply to the empty string. The WeChat server will not handle this and will not initiate a retry. For details, please see "Send Message-Passive Reply Message".
3. If the developer needs to respond to user messages immediately within 5 seconds, that is, when using the "Send Message-Passive Reply Message" interface to passively reply messages to the user, the message encryption can be set at the developer center of the official website of the public platform. After the encryption is enabled, the messages sent by the user and the messages replied by the developer will be encrypted (but the developer sends messages to the user through API calls such as customer service interfaces, which will not be affected).