Skip to main content
Webhooks push order updates to you in real time, so you don’t have to poll. When an order changes status, Sparqle sends an HTTP POST to the URL you’ve registered for that event.

Setup

Webhook URLs are configured per company and per event (status). Provide your endpoint(s) to your Sparqle contact, specifying which statuses you want to receive. You can register different URLs for different statuses, or one URL for all of them.
Webhooks are environment-specific. Register your production endpoint against the live environment separately from any test endpoint.

The request

Sparqle sends a POST with a fixed JSON payload. The shape is stable — fields won’t be removed or renamed as the platform evolves.
Match incoming webhooks to your own records on orderRef (your reference) or orderId (Sparqle’s). The status field tells you which lifecycle stage the order just entered; previousStatus lets you ignore out-of-order or duplicate deliveries.

Responding

Return a 2xx status code as quickly as possible to acknowledge receipt. Do any heavy processing asynchronously after you’ve responded — a slow endpoint can cause retries or timeouts.

Best practices

  • Be idempotent. The same status may be delivered more than once; dedupe on orderId + status.
  • Don’t assume ordering. Network timing means events can arrive out of order. Trust the status value, and ignore transitions that move backwards.
  • Verify the source. Restrict your endpoint to Sparqle (for example with a shared secret path or an allowlist) and only accept expected statuses.