# Receive events by webhook

Missed call, text received, voicemail: your server is notified.

- Role: Manager
- Duration: 3 min
- On: Web
- Learning Centre: https://callizy.ca/en/apprendre/webhooks
- Integrations path · Lesson 8
- Open this screen in Callizy: https://app.callizy.ca/en/manager?view=integrations
- The page on callizy.ca: https://callizy.ca/docs

## Before you start

- Be a manager on the Callizy account.
- A public https address that receives POST requests: your server, or a tool like Make.

## Step by step

5 steps, about 3 min.

Screenshots show Callizy in French. Button names are given in English.

### 1. Open the Webhooks tab (10 s)

In **Developers**, **Webhooks** tab, click **New webhook**.

Menu: Administration › Settings › Developers › Webhooks

### 2. Name and address (30 s)

**Name**: what it is for, for example “Missed calls”. **Destination URL**: the address that will receive the events.

### 3. Pick the events (30 s)

Under **Events to listen for**, check what you need among 17: **Missed call**, **Voicemail received**, **SMS received**, **Summary ready**, **Appointment booked**… Then **Create**: “Webhook created.”

### 4. Test (20 s)

On the webhook card, click **Test**. The result shows below, for example “Your endpoint answered HTTP 200: test received.”

### 5. Check the signature (1 min)

Each delivery carries the **X-Callizy-Signature** header: an HMAC-SHA256 of the raw body, computed with the card’s **Signing secret**. Click **Reveal** to see it and copy it, at any time.

## Key points

- 17 events: calls, voicemails, texts, contacts, appointments and tasks.
- A failed delivery is retried for nearly three days; after 5 days of failures, the webhook is paused.
- The Zaps that listen to Callizy also show up in this tab.

## Not working?

### Callizy shows “Invalid URL”

1. Enter a full address that starts with https://.

### Callizy shows “Pick at least one event”

1. Check at least one event under **Events to listen for**.

### Callizy shows “Your endpoint answered HTTP 401: it refused the test”

1. Your endpoint requires an Authorization header: accept requests without one, Callizy signs each one with X-Callizy-Signature.

### Callizy shows “Your endpoint didn’t answer within 10 seconds”

1. Answer right away with a 200, then process the event afterwards.

### Callizy shows “This address can’t receive webhooks: it isn’t public”

1. Use an address reachable from the Internet: not localhost, and not an internal network address.

### The card shows recent failures

1. Click **Test** to see your endpoint’s response.
2. After 24 h of failures, managers get an email; after 5 days, the webhook is paused: fix the address, then click **Activate**.

## Frequently asked questions

### Where can I see the delivery history?

Not in the app yet: the API gives the last 30 days, GET /api/v1/webhooks/deliveries/.

### Why are there “Zapier …” webhooks?

Each Zap that listens to Callizy creates one. Delete the Zap in Zapier rather than the webhook.

### Is it included in my subscription?

Yes, in every plan, from Solo.

Updated October 27, 2026.