# Verification Ticket
After the application for creation of a third-party platform is approved, the Weixin server will push a verification ticket (component_verify_ticket) to the third-party authorization event receipt address every 10 minutes using the POST
method.
After receiving the POST
request, the third-party platform just needs to return the string success
. To enhance security, the xml in postdata is encrypted with the encryption/decryption key entered during the service application. For details, see the Technical Solution for Encryption/Decryption. Received push messages must be decrypted (for details, see Message Encryption/Decryption Access Guide).
# Parameters
Parameter | Type | Field Description |
---|---|---|
AppId | string | Third-party platform's AppID |
CreateTime | number | Timestamp (in sec) |
InfoType | string | Always set to "component_verify_ticket" |
ComponentVerifyTicket | string | Ticket content |
Example of decrypted push content:
<xml>
<AppId>some_appid</AppId>
<CreateTime>1413192605</CreateTime>
<InfoType>component_verify_ticket</InfoType>
<ComponentVerifyTicket>some_verify_ticket</ComponentVerifyTicket>
</xml>
Note:
The component_verify_ticket has a longer validity period than the component_access_token. We recommend you save the most recently available component_verify_ticket. Before the component_access_token expires, you can directly use the component_verify_ticket to update it, avoiding the situation where the component_access_token cannot be updated due to failure to receive the component_verify_ticket.