Webhooks

Webhooks allow you to receive HTTP callbacks when events occur in your Liveday account. Instead of polling the API, you configure a URL and Liveday will send a POST request to it whenever a subscribed event fires.

Setup

Webhooks are configured through the Integrations section of your Liveday dashboard. Create a new webhook integration, provide a URL, and select which events you want to subscribe to.

Events

Delivery

When an event fires, Liveday sends an HTTP POST request to your configured URL with the event payload as JSON.

Headers

Every webhook request includes these headers:

Example payload (OrderCompleted)

{
  "uuid": "a1b2c3d4-e5f6-7890-abcd-ef1234567890",
  "email": "anna@example.com",
  "phone_number": "+46701234567",
  "shipping": {
    "name": "Anna Svensson",
    "address": "Storgatan 1",
    "city": "Stockholm",
    "postal_code": "11122"
  },
  "billing": null,
  "terminal_id": null,
  "order_id": "ord_abc123",
  "transaction_id": "txn_xyz789",
  "payment_intent": "pi_stripe_123",
  "original_order_uuid": null,
  "is_refunded": false,
  "total_price": 59800,
  "payment_method": "card",
  "payment_method_brand": "visa",
  "split_payment_methods": null,
  "control_code": null,
  "control_server_id": null,
  "control_server_terminal_id": null,
  "live_sales_point_id": null,
  "live_sales_point_table": null,
  "live_sales_point_status": null,
  "cart": {
    "organization": "your-org-id",
    "event": "evt_summer2026",
    "currency": "SEK",
    "items": [
      {
        "product_type": "Ticket",
        "name": "General Admission",
        "quantity": 2,
        "price": 29900,
        "vat": 6.0,
        "event": "evt_summer2026",
        "event_name": "Summer Festival 2026",
        "section": "sec_ga",
        "section_name": "General Admission",
        "row": null,
        "seat": null,
        "item_id": "item_abc",
        "category": "ticket"
      }
    ],
    "total_price": 59800,
    "original_price": 69800,
    "campaigns": [
      {
        "uuid": "camp_earlybird",
        "name": "Early Bird",
        "code": "EARLY2026",
        "discount_amount": 10000
      }
    ]
  },
  "created_at": "2026-03-01T14:30:00Z",
  "order_number": 10042,
  "order_source": "webshop",
  "refund_reason": null,
  "refund_reason_comment": null,
  "settled_status": null
}

Responding

Your endpoint should return a 2xx status code to acknowledge receipt. Any other status code is treated as a failure and triggers a retry.

Retries

Failed deliveries are retried with exponential backoff:

• Maximum 5 retry attempts per delivery
• Backoff includes ±15% jitter to avoid thundering herds
• After all retries are exhausted, the delivery is marked as PermanentlyFailed

Delivery statuses

Monitoring deliveries

You can monitor webhook delivery status through the API:

List deliveries

curl -G "https://api.liveday.se/webhooks/deliveries" \
  -H "Authorization: Bearer sk_your_api_key"

Get delivery details

curl "https://api.liveday.se/webhooks/deliveries/{delivery_uuid}" \
  -H "Authorization: Bearer sk_your_api_key"

Get delivery attempts

curl "https://api.liveday.se/webhooks/deliveries/{delivery_uuid}/attempts" \
  -H "Authorization: Bearer sk_your_api_key"

Each attempt record includes the HTTP status code, response body (truncated to 5000 characters), duration in milliseconds, and any error message.

Payload reference

OrderCompleted fields

Cart object

Cart item object

Campaign object

Best practices

• Verify the event type — check the X-Webhook-Event-Type header before processing
• Use the delivery ID for idempotency — the X-Webhook-Delivery-ID header uniquely identifies each delivery; use it to avoid processing duplicates
• Return 2xx quickly — acknowledge receipt immediately and process asynchronously if needed
• Handle retries gracefully — your endpoint may receive the same event multiple times if a previous acknowledgement was lost