Skip to main content
Webhooks allow your application to receive real-time notifications when important events happen in your Quickbutik store. Instead of constantly polling the API, webhooks notify your application when events occur, usually within a minute.
Common use cases:
  • Sync new orders to your fulfillment system
  • Update inventory levels across multiple platforms
  • Send custom order confirmations or notifications
  • Trigger automated workflows and integrations

How Webhooks Work

When an event occurs in your store (like a new order), Quickbutik sends an HTTP GET request to your configured webhook URL with event details as query parameters.

Quick Setup

1

Create webhook endpoint

Set up an endpoint in your application to receive webhook notifications
2

Configure in Quickbutik

Enable webhooks in your Quickbutik Control Panel under Settings → Webhooks and add your endpoint URL
3

Handle events

Process the webhook events in your application based on the event type

Event Structure

All webhook requests are sent as GET requests with the following query parameters: If your webhook URL already contains a query string, its own parameters are kept, and all of the parameters above except id are added to them.

Example Webhook Request

Delivery

  • A job sends new events once a minute, oldest first, so a request usually arrives within a minute of the event. When many events are queued it can take longer.
  • Each event is sent once to every URL of every active webhook that listens to it.
  • Quickbutik waits at most 10 seconds for your endpoint and does not look at the response. A request that fails or times out is not retried.

Complete Example

Here’s a complete webhook handler that processes different event types:

Best Practices

Respond Quickly

Respond within 10 seconds. Quickbutik closes the request after 10 seconds. Process the actual work asynchronously.

No Retries

Failed requests are not sent again. If your endpoint is down or too slow, the event is lost. Poll the API as a backup for critical data.

Validate Events

Check the securityhash parameter on every request to make sure it comes from your store.

Error Handling

Implement proper error handling and retry mechanisms for failed webhook processing.
Important Considerations:
  • Webhooks are sent as GET requests (not POST)
  • Failed or timed-out requests are not retried
  • The same event can occasionally arrive more than once, so make your processing idempotent
  • Use the API to fetch complete data when processing webhooks

Testing Webhooks

Use tools like ngrok to test webhooks locally:

Next Steps

Event Types

Explore all available webhook events and their data

Setup Guide

Detailed webhook configuration and troubleshooting