Home / Integrations / Webhooks

Send every booking to your own system.

When Ringmere books an appointment, moves one, or hands a call to your team, it can tell your software in real time. Signed webhooks, on every plan.

Start your free trial All integrations

Ringmere webhooks send an HTTPS POST to a URL you choose whenever the AI receptionist books, reschedules or cancels an appointment or a table, or hands a call to your team. Each request is signed with HMAC-SHA256 so you can verify it came from Ringmere, carries a stable event id so you can ignore duplicates, and is retried if your endpoint is down. It is included on every plan.

How it works

One URL, and your system hears about every call that matters.

Add your endpoint

In Settings, open Calendar and find “Send bookings to your own system”. Enter a public HTTPS URL. Your signing secret is shown once, so copy it when you see it.

Send a test event

Press “Send test event” and Ringmere posts a test payload to your URL, so you can build and check your handler before a real call arrives.

Verify and process

Check the signature header against the raw request body using your secret, use the event id header to ignore repeats, and return a 2xx status to acknowledge.

Events

appointment.booked, appointment.rescheduled and appointment.cancelled
order.placed, order.updated and order.cancelled, for restaurants that take orders as well as reservations
handoff.created, when a call is escalated to your team

Delivery details

The body is JSON: the event name, your business id, the time the event happened, and the data for that event.
Three headers: x-ringmere-event, x-ringmere-event-id and x-ringmere-signature, a hex HMAC-SHA256 of the raw body.
A failed delivery is retried with backoff. A 4xx response is treated as final and not retried, except 408 and 429.
Your endpoint must be public HTTPS. Redirects are not followed.
The setting lives with the calendar, so it is available to appointment businesses and to restaurants that take reservations.
To make bookings or read your calls and customers from your own system, use the REST API below.

The REST API

Read your calls, bookings, customers and messages for the team, make bookings and mark messages done, with an API key you make and revoke in Settings, Calendar, under API keys and webhooks.
A booking made through the API goes through the same checks as one made on a call: opening hours, staff hours, notice, the diary and a connected calendar.
Each key has scopes: read, write, and call transcripts only when you grant them. A key belongs to one business and is shown once, when it is made.
Subscribe to events such as call.completed, appointment.booked and handoff.created with REST hooks, each signed with its own secret.
The API is for servers, not browsers. The API reference has every endpoint, limit, error and event, with signature checks in Node and Python.

Connect to Zapier and thousands of apps

No code needed. In Zapier, create a Zap with the Webhooks by Zapier trigger set to Catch Hook. Zapier gives you a hook URL.
Paste that URL into Ringmere as your webhook (Settings, Calendar, "Send bookings to your own system"), then press "Send test event" so Zapier captures the shape.
From there, route every booking, reschedule, cancellation and handoff wherever you work: a CRM, a Google Sheet, Slack, email, and thousands more.
This route is one way, data OUT of Ringmere. An official Ringmere app in the Zapier directory is planned, and is not published yet.
Not sure which route fits? Connecting an AI receptionist to your CRM compares webhooks, the API, REST hooks and Zapier in plain terms.

Questions

Webhooks, plainly answered.

Does Ringmere have webhooks?

Yes, on every plan. Ringmere posts booking, reschedule, cancellation and handoff events to an HTTPS URL you choose, signed with HMAC-SHA256 and retried on failure.

How do I verify a webhook came from Ringmere?

Compute an HMAC-SHA256 of the raw request body using the signing secret shown when you set the webhook up, and compare it with the x-ringmere-signature header. Reject the request if they differ.

Will I receive the same event twice?

You can, because a delivery that fails is retried. Every attempt at the same event carries the same x-ringmere-event-id, so store the ids you have processed and skip repeats.

Does Ringmere have an API or work with Zapier?

Yes to an API. Every plan includes a REST API that reads your calls, bookings, customers and messages for the team, makes bookings and marks messages done, plus signed webhooks and REST hooks that tell your own system when something happens. For Zapier, the Webhooks by Zapier “Catch Hook” trigger works today: point a Ringmere webhook at it and bookings, changes and messages flow into Zapier and on to thousands of apps. An official Ringmere app in the Zapier directory is planned, and is not published yet.

Keep reading

Stop missing calls. Start booking them.

Put Ringmere on your line today and never lose another booking to a missed call.

Call answered2:47am · first ring

Booked in your calendarCut & blow dry · 2:30pm

£42 recoveredWhile you slept

Start your 7-day free trial Talk to us