Developer documentation

Connect Meetzi to the tools you use. Read booking data and receive events when bookings are created, rescheduled, or cancelled.

REST APIJSON responsesAPI key authenticationWebhooks

Build custom integrations with Meetzi's booking automation API. Validate an account, list booking pages, read recent bookings, and subscribe to live booking events. All seven endpoints use a Meetzi API key and are available under /v1.

Zapier and custom server integrations use the same /v1/* endpoints, authentication, and booking payloads.

01 · Connect your account →Generate an API key and make your first authenticated request.02 · Read booking data →Find recent bookings, cancellations, and rescheduled appointments.03 · Subscribe to events →Send booking events to a webhook URL, for one page or all your pages.04 · Understand the payload →Explore guest details, meeting information, and custom question answers.

Base URL

https://api.meetzi.co

Use HTTPS for all API requests. Request and response bodies use JSON, except successful subscription deletion, which returns no body. Paths in this reference are relative to this base URL.

Make your first request

1. Open Meetzi → Integrations.
2. Connect Zapier and generate your API key. Copy the full key when it appears; it is shown only once.
3. Set MEETZI_API_KEY in your local environment, then test the connection:

API keys are currently generated from the Zapier integration screen in Meetzi. You can use that key with your own server integration as well.

cURL

curl --request GET 'https://api.meetzi.co/v1/me' \
  --header "Authorization: Bearer $MEETZI_API_KEY"

JavaScript

// Run on your server with MEETZI_API_KEY set in the environment.
const response = await fetch('https://api.meetzi.co/v1/me', {
  headers: { Authorization: `Bearer ${process.env.MEETZI_API_KEY}` },
});
if (!response.ok) throw new Error(`Meetzi API returned ${response.status}`);
const account = await response.json();
console.log(account.displayLabel);

A successful request returns 200 OK and your connection identity. All examples in this reference use fictional accounts and identifiers; replace them with values returned by your own account.

Endpoint directory

Method	Endpoint	Purpose
GET	/v1/me	Validate a key and identify the connected account.
GET	/v1/booking-pages	List owned booking pages and their custom questions.
GET	/v1/triggers/new-bookings	List recent bookings with status booked.
GET	/v1/triggers/cancelled-bookings	List recent cancelled bookings.
GET	/v1/triggers/updated-bookings	List recent rescheduled bookings.
POST	/v1/subscriptions	Subscribe to a booking event.
DELETE	/v1/subscriptions/{id}	Deactivate a webhook subscription.

Build an integration

1. Validate the key and identify the account with /v1/me.
2. Use /v1/booking-pages to select a page and discover its custom questions.
3. Read recent matching bookings from the trigger endpoints to preview the data your integration will receive.
4. Create a subscription with /v1/subscriptions and the URL of your HTTPS webhook receiver. Store the returned subscription ID.
5. Process incoming booking payloads, then delete the subscription with /v1/subscriptions/{id} when you no longer need events.

Live events arrive at your webhook receiver. The trigger list endpoints return recent matching bookings rather than a complete event history. Zapier follows this same lifecycle when a Zap is enabled or its subscription is removed.

Booking event	Subscription trigger_type	Recent records endpoint
Booking Created	new_booking	/v1/triggers/new-bookings
Booking Cancelled	booking_cancelled	/v1/triggers/cancelled-bookings
Booking Rescheduled	booking_updated	/v1/triggers/updated-bookings

Access & conventions

• Ownership: booking data is scoped to pages owned by the connected user. Being assigned as a host does not grant access to another user's pages through these endpoints.
• Time: computed start and end times are ISO 8601 UTC strings. duration is measured in minutes.
• Empty results: list endpoints return { "data": [] } when there are no matching records.
• Optional data: fields such as guest email, host details, and meeting information can be null.
• API surface: this reference covers the API key authenticated automation endpoints. Product session endpoints are outside this API reference.

Download the OpenAPI 3.1 specification to explore the API in compatible developer tools, or continue with authentication.