API and webhooks
Connect Gaurify Meet to the tools you already use. Read your bookings, offer your times, and hear about every booking the moment it happens.
API keys
Create a key in the app: Settings, Developer, Create API key. You see it once, so copy it then. Send it on every call:
Authorization: Bearer gm_live_...
Every call is about the key's owner only. A key never reaches anyone else's data. Turn a key off any time in the same place.
Endpoints
All paths start at https://meet.gaurifyhq.com and answer in JSON.
/api/v1/meWho the key belongs to, and their booking page link.
/api/v1/bookingsYour meetings, newest first. Filters: status (upcoming, past or all), since (an ISO time; bookings made then or later) and limit (1 to 100). Upcoming comes soonest first.
/api/v1/bookings/{id}One of your bookings, in the same shape as a webhook, plus status.
/api/v1/bookingsBook a meeting on your calendar. Send start, duration, name and email. Add eventType (a slug) to use a meeting type.
/api/v1/bookings/{id}/cancelCancel one booking. The guest is told and the time opens again. A paid one is refunded in full. Body: reason, optional.
/api/v1/event-typesYour active meeting types: id, name, slug, duration_min, mode, location and price.
/api/v1/availabilityOpen times. Send duration in minutes (or type, a slug), and from and to as ISO times or plain dates. Add tz, like Asia/Kolkata: plain dates are read in it, and local gives every time in it. It defaults to your zone.
/api/v1/hooksSend one event to a URL. Body: target_url and event. Returns its id.
/api/v1/hooksYour hooks and webhooks, with how each one is doing.
/api/v1/hooks/{id}Stop sending to that URL.
/api/v1/hooks/sampleUp to 3 recent bookings, shaped exactly like a delivery. Add ?event= to pick the event.
Events
booking.createdwhen someone books, or you make a meeting.booking.cancelledwhen a meeting is cancelled, by you or your guest.booking.rescheduledwhen a meeting moves to a new time.booking.paidwhen a paid booking's payment comes in.
Each delivery is one JSON POST. id is new for every delivery. data.id is the booking. Every event carries the same full booking, so a field you map once works for all four.
Example payload, a paid booking. amount is in the smallest unit, so 150000 means 1500.00 INR.
{
"id": "6f1c0b3e-2a7d-4c55-9a51-7f0f9d2a8e10",
"event": "booking.paid",
"version": 2,
"created_utc": "2026-10-07T09:30:00.000Z",
"data": {
"id": "b7d2...",
"start_utc": "2026-10-09T06:00:00.000Z",
"end_utc": "2026-10-09T06:30:00.000Z",
"duration_min": 30,
"mode": "meet",
"location": "google_meet",
"meet_url": "https://meet.google.com/abc-defg-hij",
"guest_name": "Asha Rao",
"guest_email": "asha@example.com",
"guest_phone": "+919800000000",
"guest_tz": "Asia/Kolkata",
"note": "About the launch",
"answers": [{ "label": "What is this about?", "value": "Our launch" }],
"event_type": { "id": "et_1a2b", "name": "Intro call", "slug": "intro-call" },
"event_type_id": "et_1a2b",
"team_type": null,
"manage_url": "https://meet.gaurifyhq.com/manage/...",
"amount": 150000,
"currency": "INR",
"payment_status": "paid",
"payment_id": "pay_Nx4kQ2a8b9",
"by": "guest",
"created_utc": "2026-10-07T09:30:00.000Z"
}
}
locationisgoogle_meet,phone,link(your own Zoom or Teams link) orvideo(a Gaurify video room).byisguest,hostorsystem.- A move adds
previous_start_utc, the real old start. - A cancel adds
reason:rebook_requestedwhen you asked the guest to pick a new time,account_closed, the words you sent to the cancel endpoint, ornull. - A paid booking fills
amount(in the smallest unit),currencyandpayment_status(paidorrefunded), and addspayment_id.
Keep the manage link private. manage_url lets anyone who has it move or cancel that booking. It is sent only to your own endpoints, because you own the booking. Never show it to anyone but the guest.
Changed on 7 October 2026 (version 2). "Ask the guest to rebook" used to send booking.rescheduled. It now sends booking.cancelled with reason: "rebook_requested", since the booking is gone and has no new time. Every v1 key still arrives.
Check the signature
Every delivery carries X-Gaurify-Signature: the HMAC-SHA256 of the raw body, in hex, made with your secret. X-Gaurify-Event names the event. Check it before you trust the body:
import crypto from "node:crypto";
function isFromGaurify(rawBody, signature, secret) {
const want = crypto.createHmac("sha256", secret).update(rawBody).digest("hex");
return signature.length === want.length &&
crypto.timingSafeEqual(Buffer.from(want), Buffer.from(signature));
}
Answer with any 2xx within 5 seconds. After 20 failures in a row we pause the hook and tell you in the app.
The Gaurify Meet app on Zapier
Connect Gaurify Meet to 7,000+ apps with no code. Triggers: new, cancelled, rescheduled and paid bookings. Actions: create or cancel a booking, find a booking, find an open time.
Add Gaurify Meet to your Zapier account. It is in beta while Zapier reviews it.
Use with Zapier or Make: REST hooks
Zapier and Make subscribe a URL when a Zap or scenario turns on, and remove it when it turns off. Map them like this:
- Subscribe:
POST /api/v1/hookswith the platform's target URL and one event. Keep theid. - Unsubscribe:
DELETE /api/v1/hooks/{id}. - Sample data:
GET /api/v1/hooks/sample, with?event=set to the event. - Auth: an API key field, sent as the Bearer header above.
If your hook URL answers 410 Gone, we remove that hook for you.
For dropdowns, list GET /api/v1/event-types and GET /api/v1/bookings?status=upcoming.
Questions
Write to hello@gaurifyhq.com. We read every note.