Knowledge base
Integrations

Webhooks & API

Updated 21 July 2026

Webhooks & API Keys

CaterCloud can push real-time data to your other tools — Slack, Zapier, Make, or any custom endpoint — using outbound webhooks. This is useful for any catering business that wants booking updates, new quotes, or invoice events to flow automatically into the rest of their stack.

---

Setting Up a Webhook

Navigate to Settings → Webhooks to get started.

  1. Fill in the Name field — something descriptive like Slack #updates or Zapier booking flow.
  2. Enter your Destination URL (where we post the data) — this is the endpoint that will receive the payload.
  3. Under Events to subscribe to, click one or more event tags to select them. Selected events are highlighted in navy; click again to deselect.
  4. Click Create webhook.

Copy Your Signing Secret Immediately

After the webhook is created, CaterCloud displays a signing secret once. Use the Copy button to save it now.

> ⚠️ This secret is not stored in a recoverable form. If you lose it, you'll need to delete the webhook and create a new one.

Use the secret in your receiving endpoint to verify that payloads are genuinely from CaterCloud.

---

Managing Existing Webhooks

Your active webhooks appear in a table showing:

  • Name and creation date
  • URL the payloads are sent to
  • Events the webhook is subscribed to
  • Last delivery date
  • Status and any recent errors

From the Actions column you can:

  • Enable or disable a webhook without deleting it
  • Rotate the secret — a new signing secret is generated and shown once; update your endpoint immediately
  • Delete a webhook permanently (you'll be asked to confirm)

---

If Deliveries Are Failing

Check the Last delivery and error details in the webhook table. Common causes are an unreachable URL or a misconfigured secret on the receiving end. Disable the webhook, fix the endpoint, then re-enable it.

---

Tip: If you're connecting to Zapier or Make, use their provided webhook URL as your Destination URL and store the signing secret in their header/auth settings for verified delivery.

Still stuck? Open the chat assistant (bottom-right) for help with your specific setup.