MCS webhooks best practices
Follow these best practices when implementing MCS webhooks.
Handle duplicate events
Use eventId to identify and deduplicate webhook events. Because the same event may be delivered more than once, design your integration to process repeated deliveries safely.
Return a successful response
Return an HTTP 200 OK response after receiving a webhook notification. Process the payload asynchronously to help prevent request timeouts.
Secure webhook endpoints
Use HTTPS for all webhook endpoints and validate incoming requests according to your organization's security requirements.
Log webhook activity
Record webhook activity, including eventId, eventType, the event timestamp, and processing status. These details can support troubleshooting and operational monitoring.
Handle delivery retries
Webhook deliveries may be retried if a successful response is not received. Ensure your integration can process repeated deliveries without creating duplicate downstream actions.
Monitor webhook endpoint health
Monitor webhook endpoints and configure alerts to identify delivery or processing issues. Ensure endpoints remain highly available and respond within expected timeout limits.
Support
For questions about MCS webhooks, contact your Walmart representative.
Updated about 2 hours ago

