Set up your Performance webhooks endpoint

Use one unified webhook endpoint for all Performance notifications. Walmart publishes a single event type, and your service routes by the variant in the payload.

Event model

  • Event type: SELLER_PERFORMANCE_NOTIFICATIONS

  • Variant indicator: payload.notificationType

    • ALARMS — daily shipping risks and actions
    • REPORT — weekly KPI rollup across standards

Why a unified endpoint

  • One place to scale, monitor, and rotate secrets
  • Simpler subscription management
  • Consistent verification and idempotency rules

How to route inside your service

Inspect payload.notificationType on receipt and hand off to the correct workflow.

  • ALARMS → fulfillment and order operations
  • REPORT → analytics and account health

Always deduplicate using a delivery identifier such as eventId.

How to configure

For complete steps, use Subscribe to performance webhooks.
Include the required resource value when subscribing. Use Get event types to confirm the exact value.

API reference: Get event types, Create subscription, Update subscription, Get all subscriptions, Delete subscription.

Subscribe (recommended)

Register a callback URL for the unified endpoint. Example below:

{ "events": [ { "eventType": "SELLER_PERFORMANCE_NOTIFICATIONS", "eventVersion": "V1", "resourceName": "FEEDS", "eventUrl": "https://example.com/webhooks/walmart/performance", "status": "ACTIVE" } ]
}

Recommended practices

  • Verify signatures and timestamps before routing.
  • Approved solution providers can subscribe to seller accounts who have given them access to theFEEDS scope.
  • Store the payload and return 2xx only after a durable write.
  • Keep handlers idempotent and safe to retry.
  • Monitor 2xx rate, retries, and signature failure rate.

Next steps

Reference guide

This guide helps you decide between a single unified endpoint or per event endpoints and shows how that choice affects routing and operations.

See also