Webhooks let your raffle site notify your own systems whenever something interesting happens: a customer signs up, an order completes, an instant win pays out. They’re how you wire Turbo IT into Zapier, n8n, Slack, your CRM, or a custom backend without us building a one-off integration each time.

Events we’ll emit

• customer.created — a new user account is registered.
• customer.updated — profile or marketing-preference change.
• order.created — order placed (before payment settled).
• order.paid — payment confirmed; tickets issued.
• order.refunded — order or partial-line refunded.
• competition.drawn — main draw completed; winner chosen.
• instant_win.claimed — instant-win prize awarded to a customer.
• withdrawal.requested / withdrawal.paid — wallet withdrawal lifecycle.

Payload format

Each delivery is a JSON POST to your endpoint with:

{
  "id": "evt_01HZX...",
  "type": "order.paid",
  "created_at": "2026-05-14T18:32:01Z",
  "data": {
    "order_id": "ord_01HZX...",
    "customer_id": "cus_01HZW...",
    "total_pence": 4900,
    "competition_id": "cmp_01HYY..."
  }
}

Plus a Turbo-IT-Signature header — an HMAC-SHA256 of the raw body using your secret. Verify it before trusting the payload.

Subscribing your endpoint

1. Email info@turboit.uk with your HTTPS endpoint URL.
2. We’ll register the subscription and reply with your signing secret.
3. You build your endpoint, verify the signature on each request, and respond with a 2xx status within 10 seconds.
4. If your endpoint is slow or down, we retry with backoff (1m, 5m, 30m, 2h, 24h). Persistent failures are surfaced in your admin webhook log.

Common automation patterns

• Slack alerts — pipe order.paid + instant_win.claimed into a Slack channel for live team visibility.
• CRM sync — customer.created and customer.updated mirror your audience into HubSpot/Klaviyo/Mailchimp.
• Fulfilment automation — order.paid for prize draws with a physical prize triggers a Shopify draft order or a label-printing flow.
• Fraud monitoring— pipe events into your own anti-fraud rules. Spot “same card, 20 accounts in an hour” patterns we can’t catch on a single tenant.

Until webhooks land — the CSV-pull workaround

Today’s supported path is:

1. Pull Admin → Reports → Orders export daily on a cron.
2. Diff against your last-known order ID set; the new rows are your “new orders” signal.
3. Drop those into your CRM / Slack / fulfilment pipeline.

Reliable, just batchy. Webhook delivery is the obvious upgrade path. See Reports overview.

Related: Reports overview · Integrations overview.