POST request to your configured HTTPS URL when selected resources change. Use webhooks to sync downstream systems; fetch full records with the REST API.
Delivery model
- You can configure one or more HTTPS endpoints per environment. Each endpoint receives the event types subscribed for that destination.
- Route on the payload field
event(for example"customer.created"). We do not send a separate event-type header. - Configure sandbox and production separately. Prefer distinct URLs across environments. If sandbox and production must share one URL, ask your WizCommerce contact how environment is identified for your account.
Content-Type: application/json- HTTPS with a valid TLS certificate is required.
Security
A custom header can be configured on webhook requests (for example Bearer token, API key, or shared secret in a header such aswebhook-secret or X-Webhook-Key).
HMAC-SHA256 signing of the raw request body is also supported. Header name (for example X-WC-Signature), encoding, and shared secret are agreed when the endpoint is configured.
Verify every request. Do not expose credentials publicly.
Your response
Return 2xx as soon as you have accepted the event for processing. Do heavy work asynchronously if needed.
Retries
Delivery is at-least-once. Failed deliveries retry with exponential backoff, up to 5 times (~15 minutes total):Idempotency
The sameid may be delivered more than once. Deduplicate on payload id before applying side effects.