Appointment booking API and calendar webhooks
Meetz doesn't make you watch the dashboard to know what's going on. Register a URL and you'll receive every booking, reschedule and cancellation as it happens; with the organisation key you can also query Meetz from your own code.
Three events
booking.created, booking.rescheduled and booking.cancelled. You choose which ones each webhook wants and can have several pointing at different systems.
Signed, with retries
Every notification arrives signed with HMAC-SHA256 and your webhook's secret. If your server doesn't respond, Meetz retries with growing waits and records each attempt.
Logs and a test from the dashboard
From Integrations you see each webhook's deliveries with their status and HTTP code, and fire a test event before wiring up anything real.
What each notification carries
The body includes the booking's id, the lead's name, email, phone number and timezone, the event type, the calendar, the closer with their email, start and end, the link's tracking parameters and the form answers with the question as the key. Reschedules add the previous time, the new one and the video call link; cancellations add the reason. All of them state the source of the change: lead link, dashboard or Google Calendar.
Verifying the signature
Each request carries the X-Meetz-Event, X-Meetz-Timestamp and X-Meetz-Signature headers. The signature is the HMAC-SHA256 of the body, exactly as received, with the secret Meetz gave you when the webhook was created. Compare it with your own before processing anything and drop whatever doesn't match. The URL must be public: Meetz rejects internal addresses and doesn't follow redirects.
The API with your key
With the X-API-Key header you can check the connection, list your active calendars with their booking link already built, look up a phone number's confirmed meetings and register or delete webhooks without going through the dashboard. Availability and booking creation go through the same endpoints the Meetz public page uses. The limit is 600 requests per minute per key.
Frequently asked questions
Both in Integrations. The organisation key can be regenerated, and each webhook shows its secret to copy.
Yes. Integrations has a panel with the endpoints, curl examples and the code to verify the signature.
Up to three attempts: the second after five seconds and the third half a minute later. Each one is kept in the delivery log.
Stop routing leads by hand
Connect your Google Calendar, add your closers and start taking bookings the same day. Free to start.
no card · Google Calendar in 1 click