Webhooks

Webhooks are how Sellvik pushes events to your system: an order was placed, an order was fulfilled, a product's stock dropped past a threshold. The alternative — polling — burns rate limit and adds latency. If you need near-real-time state, use webhooks.

How they work

1. You register a webhook URL and the events you care about (panel, or Webhooks management API).
2. Sellvik returns a secret once. Store it.
3. When a relevant event fires, Sellvik HTTPs POSTs a signed JSON payload to your URL within seconds.
4. Your endpoint responds 2xx. If it doesn't, Sellvik retries with exponential backoff for ~24 hours.

Where to read next

• Events — the catalogue of event names and payload shapes.
• Signing and verification — how to verify the X-Sellvik-Signature header.
• Delivery and retries — what "delivered" means, retry schedule, what 4xx/5xx do.
• Registering — panel vs API; URL hygiene.

Cheat sheet

POST /your/webhook/endpoint
Content-Type: application/json
X-Sellvik-Signature: t=1716810000,v1=a1b2c3...
X-Sellvik-Event: order.created
X-Sellvik-Event-Id: evt_a1b2c3...
X-Sellvik-Shop: acme
User-Agent: Sellvik-Webhooks/1.0

{
  "id": "evt_a1b2c3...",
  "type": "order.created",
  "createdAt": "2026-05-27T13:45:00.000Z",
  "shopSubdomain": "acme",
  "data": { /* event-specific payload */ }
}

Respond 200 OK (or any 2xx) within 10 seconds. Anything else triggers a retry.