Skip to main content

Outbound webhooks

Receive platform events at your own URL. Outbound webhooks are part of the Enterprise plan. Configure subscriptions in Settings → Integrations → Webhooks. Each subscription has its own HMAC-SHA256 signing secret displayed once on creation.

Event delivery

Events POST a JSON body to your URL. The platform signs the body with HMAC-SHA256 and sets:

X-Kennel-Event: booking.created
X-Kennel-Delivery: 01HTZ...
X-Kennel-Signature: sha256=<hex digest>

Verifying signatures (Node.js)

import crypto from 'node:crypto';

function verify(req, secret) {
  const sig = req.headers['x-kennel-signature']; // 'sha256=<hex>'
  const expected = 'sha256=' + crypto
    .createHmac('sha256', secret)
    .update(req.rawBody) // raw body bytes, NOT the parsed JSON
    .digest('hex');
  return crypto.timingSafeEqual(Buffer.from(sig), Buffer.from(expected));
}

Available events

The closed event registry includes booking lifecycle, payments, refunds, packs, memberships, customers, pets, vaccinations, waitlist, and tasks. Fetch the live list from /api/outbound-webhooks/events (staff-auth required).

Retries

A non-2xx response increments the row's failure_count and is recorded as last_failure_reason. Retry semantics today are best-effort; the webhooks-outbound queue handles in-flight retries.

Rotating a secret

Click Rotate secret on the webhook row to regenerate. The new plaintext is shown once; existing subscribers using the old secret will fail until they update.

Fetch Public API · OpenAPI 3.1 spec at /api/v1/openapi.json