NewMeet CREW25 Bots™: AI bots for your office, sales, marketing and website

Webhooks

Get events pushed to your server as they happen, signed so you can trust them.

Webhooks tell your systems when something happens in an organisation, so you do not have to poll the API. An owner or admin adds an endpoint in the office under Settings → Developer → Webhooks and chooses which events it receives, or all of them.

Events

type Sent when
person.added Someone is added to the team
person.archived Someone is marked as having left the team
job.created A job is created, in the office or from an online booking
job.status_changed A job moves to another status: by hand, on close-out, or by itself as below
quote.sent A quote is sent to the customer
quote.accepted A quote is accepted, by the customer online or marked by the office
quote.declined A quote is declined, by the customer online or marked by the office
quote.deleted A draft, sent or declined quote is deleted
invoice.issued An invoice is issued
invoice.paid An invoice is paid: by card online, marked paid, or paid in Xero

An endpoint on All events also receives event types added later. Handle types you do not recognise by ignoring them and answering 200.

The data of each event

data is a short summary of the record as it stood when the event happened, not the whole record. id is CREW25's id for it. number is the number people see without the organisation's prefix or padding, so job JB-00042 is 42. Amounts are whole cents.

Object Events Fields
person person.added, person.archived id, name; personType (admin, office, worker or subcontractor) on person.added only
job job.created id, number, title, status (active, or quoted when it is made from an unaccepted quote)
job job.status_changed id, number, from and status, each quoted, active, on_hold, completed or lost
quote quote.* id, number, totalCents: the quote's total before GST (the accepted option's once accepted), acceptedOptionId (null until accepted) and options: each option's id, name, totalCents, gstCents and totalIncludingTaxCents. A plain quote has one option with an empty name.
invoice invoice.* id, number, totalCents: the invoice's total including GST

Job statuses

A job is quoted (Quote: it needs a price, or a quote is out), active (work to do, scheduled or not), on_hold, completed or lost (did not go ahead). A job made from a draft or sent quote, or from an online request for a quote, starts quoted; every other job starts active. It moves by itself, sending job.status_changed, when a quote on a quoted job is accepted or an online booking on it is confirmed (active), or when every quote on it is declined (lost). Whether a job is booked or someone is on site is not a status.

Before 21 October 2026 the statuses were enquiry, scheduled, in_progress, on_hold, completed and cancelled: enquiry became new, scheduled and in_progress became active, and cancelled became lost. On 28 October 2026 new was retired: each new job became quoted if a draft or sent quote was on it, else active. Events now carry only the current values.

What your endpoint receives

A POST with a JSON body:

{
  "id": "5f0c1b9e-8d7a-4e6f-9a2b-3c4d5e6f7a8b",
  "type": "person.added",
  "createdAt": "2026-09-24T21:31:11.000Z",
  "organisationId": "org_a1b2c3d4e5f6a7b8",
  "data": {
    "object": "person",
    "id": "2c9d7e1f-4a3b-4c5d-9e8f-7a6b5c4d3e2f",
    "name": "Sam Carpenter",
    "personType": "worker"
  }
}

Each request carries these headers:

Header Value
CREW25-Event-Id The event's id. The same on every retry of one event.
CREW25-Event-Type The event's type.
CREW25-Signature t=<unix seconds>,v1=<signature>. See below.

Verifying the signature

Every endpoint has a signing secret, starting whsec_, shown in its settings. Check every request before trusting it:

  1. Split CREW25-Signature on , into t and v1.
  2. Compute an HMAC-SHA256 of <t>.<raw request body>, keyed with the signing secret, as hex.
  3. Compare it with v1 in constant time, and reject the request if they differ.
  4. Reject the request if t is more than five minutes from your clock.

Use the raw body exactly as it arrived. Parsing and re-serialising the JSON changes the bytes and the signature will not match.

import { createHmac, timingSafeEqual } from 'node:crypto';

export function verify(header, rawBody, secret) {
  const parts = Object.fromEntries(header.split(',').map((part) => part.split('=')));
  const expected = createHmac('sha256', secret).update(`${parts.t}.${rawBody}`).digest('hex');
  const fresh = Math.abs(Date.now() / 1000 - Number(parts.t)) < 300;

  return fresh && timingSafeEqual(Buffer.from(expected), Buffer.from(parts.v1 ?? ''));
}

Rotating the secret in settings replaces it immediately. Update your receiver straight away.

Responding and retries

Answer with any 2xx status within 10 seconds. Do slow work after you respond, not before.

Anything else, including a redirect or a timeout, is a failed delivery. CREW25 retries it after 1, 5, 30, 120 and 360 minutes, then gives up. Because an event can arrive more than once, use CREW25-Event-Id to ignore ones you have already handled. Events are not guaranteed to arrive in order; compare createdAt if order matters.

Settings shows the latest deliveries with their response codes, and Send test event posts a webhook.test event to check an endpoint straight away.

Endpoint requirements

Endpoints must use https:// and be reachable on the public internet. CREW25 refuses URLs that point at private or local network addresses.