Missing webhooks and order recovery
Notifications complement order queries; they do not replace them.
Prepare the receiver
Configure your own reachable HTTPS endpoint, verify signatures and event_id as documented, and acknowledge promptly before doing asynchronous processing. Do not use our homepage as your webhook address.
Recover missed updates
Account webhooks and API-key webhooks cover different events. Failed deliveries are retried, but absence of a webhook does not mean order failure. Use account-level order queries with updated_after and pagination, and deduplicate by event_id and order ID.
Configure your receiver
Enter your own receiving service in the relevant webhook settings.
- Use an externally reachable HTTPS URL.
- Choose the required order sources and event subscriptions.
- Implement signature verification and event/object checks from the current documentation.
- Durably accept the event and respond promptly, then process it asynchronously.
The receiver URL belongs to your system; it is not the zovocard homepage.
Handle duplicates and ordering
Notifications may repeat or arrive in a different order.
- Deduplicate using event_id or the identifier required by the API.
- Also guard fulfillment or credits by business order or transaction ID.
- Query the current platform status before applying an uncertain event.
If a callback is missing
Check the URL, HTTPS, gateway rules and receiver logs. Verify that the subscription covers the order source; account-level and Key-level coverage can differ. Use documented order queries and updated-time pagination to fill gaps, retaining request IDs for support.