Webhook events

This is the index of every event Cooledge can send to a webhook. When something happens in your business, Cooledge makes a signed HTTP POST to your subscription URL with the event as JSON. Each event has its own page with the exact fields it carries. This page covers what every event has in common and links to all thirteen.

If you are setting up a subscription for the first time, start with the webhooks guide. It covers managing subscriptions in the portal, verifying the signature, retries and replay. This page is the catalogue of what you can subscribe to.

The event envelope

Every event body is a single JSON object. It always starts with the same five envelope fields, then the fields specific to that event type are merged in alongside them. The envelope is what lets you route and dedupe an event without knowing its type.

A body looks like this. The five envelope fields are always present, and the rest depends on the event_type (the trailing fields below stand in for whatever that specific event carries):

{
  "version": "v1",
  "event_type": "customer.created",
  "event_id": "3b1c0e2a-7d44-4e91-9a2c-1f0b8e6d5a23",
  "business_id": "a7f3c9d1-2e84-4b6f-8c01-5d9e2a1f7b30",
  "occurred_at": "2026-06-17T03:21:44.512Z",

  "...": "event-specific fields are merged in here"
}

The exact event-specific fields live on each event's own page, linked in the table below. New fields may be added to any payload over time, so ignore fields you do not recognise rather than failing on them.

Delivery and deduping

Cooledge delivers at least once. The same event can reach you more than once, because a retry can land after your endpoint already processed the first attempt, or because you replayed it from the portal. So your handler must be idempotent.

Dedupe on event_id. The same value is on the X-Cooledge-Event-Id header, and it is stable across every redelivery and replay of the same event. Store the event ids you have already processed and skip any you have seen before.

The signature scheme, the retry and dead-letter behaviour and replaying a delivery all live in the webhooks guide. They are the same for every event type, so they are documented once there rather than repeated here.

The events

There are thirteen event types, grouped by the record they are about. Each links to its own page with the full payload shape.

Customers

Leads

Quotes

Invoices

Jobs

Bookings

Where to go next

• Webhooks covers subscriptions, signature verification, retries and replay.
• Authentication covers the scope list, including webhooks:manage for the planned subscription API.
• The API changelog records new event types and other additive changes to the contract.