canonical: https://jentic.com/apis/meetzi.co/meetzi

# Meetzi Booking Automation API

The Meetzi Booking Automation API exposes the booking pages a Meetzi account owns and the bookings guests make on them. It returns recent new, cancelled, and rescheduled bookings with guest name and email, start and end times, duration, and the meeting option such as a Google Meet link, filtered by booking page. Webhook subscriptions push one booking event to a callback URL for the new_booking, booking_cancelled, or booking_updated trigger types. Every request authenticates with a Meetzi API key sent as a bearer token, and booking data is limited to pages owned by the key holder.

## For AI agents

Read new, cancelled, and rescheduled Meetzi bookings for the booking pages an account owns, and subscribe a webhook URL to booking events so an agent reacts as soon as a guest books or changes a meeting.

## Scope

Does not create, reschedule, or cancel bookings, manage availability, or edit booking pages. Use for reading Meetzi bookings and subscribing to booking events only.

## Capabilities

- Confirm which Meetzi account an API key belongs to via GET `/v1/me` before running any automation
- List the booking pages the key owner owns, with ids to filter later booking reads
- Pull recent new bookings with guest_email, start_datetime, end_datetime, and meeting_option_url, optionally filtered by booking_page_id
- Retrieve recently cancelled and rescheduled bookings to keep a CRM or calendar mirror in sync
- Subscribe a target_url to new_booking, booking_cancelled, or booking_updated events for one page or all owned pages
- Deactivate a webhook subscription by id when an integration is retired

## Use cases

### Agent-run booking follow-up through Jentic

An assistant agent watches Meetzi for fresh bookings and drafts a follow-up for each guest. Through Jentic it searches for 'list new Meetzi bookings', calls the new-bookings trigger with a booking_page_id, and reads guest_fullname, guest_email, and start_datetime from each record. The API key stays in your own Jentic One instance, so the agent only sees booking data, never the key.

Example prompt: Call GET `/v1/booking-pages` to find the id of the page named 'Discovery Call', then call GET `/v1/triggers/new-bookings` with that booking_page_id and limit 20, and return guest_fullname, guest_email, and start_datetime for each booking

### Real-time booking webhooks

Instead of polling, an integration registers a webhook so Meetzi posts one booking object to a callback URL the moment a guest books, cancels, or reschedules. The subscription takes a required trigger_type and target_url, and an optional booking_page_id; leaving the page filter null covers every owned page, including pages created later. Deliveries carry no signature and are attempted once with no automatic retry, so the receiver should acknowledge quickly.

Example prompt: Call POST `/v1/subscriptions` with trigger_type 'booking_cancelled' and target_url 'https://example.com/webhooks/meetzi' and booking_page_id null, then store the returned subscription id

### CRM sync for cancellations and reschedules

Sales teams keep their CRM accurate by reconciling changed meetings. The cancelled-bookings and updated-bookings triggers each return up to 500 recent records per call, so a nightly job can mark cancelled meetings as lost and move rescheduled ones to their new start time. There is no cursor or offset pagination, so the job reads the latest window rather than paging back through history.

Example prompt: Call GET `/v1/triggers/cancelled-bookings` with limit 100 and GET `/v1/triggers/updated-bookings` with limit 100, then list the booking_id and new start_datetime of each rescheduled booking alongside the cancelled booking ids

### Integration health check

Before a scheduled automation runs, it can confirm the stored Meetzi key still works and points at the expected account. The identity endpoint returns the connected account, and a 401 response signals a missing, invalid, or revoked key, letting the automation stop early and alert the owner instead of silently missing bookings.

Example prompt: Call GET `/v1/me` and report the connected account identity, or report that the key was rejected if the response is 401

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/v1/me` | Get connection identity |
| GET | `/v1/booking-pages` | List owned booking pages |
| GET | `/v1/triggers/new-bookings` | List new bookings |
| GET | `/v1/triggers/cancelled-bookings` | List cancelled bookings |
| GET | `/v1/triggers/updated-bookings` | List rescheduled bookings |
| POST | `/v1/subscriptions` | Create webhook subscription |
| DELETE | `/v1/subscriptions/{id}` | Deactivate webhook subscription |

## Key resources

- **Booking pages** — Booking pages owned by the API key holder, used to filter booking reads and webhook subscriptions
- **Bookings** — New, cancelled, and rescheduled booking records with guest, time, and meeting option details
- **Subscriptions** — Webhook subscriptions that deliver one booking event per trigger type to a callback URL

## AI readiness

This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.

- **Score:** 67 / 100
- **Maturity:** AI-Aware
- **Dimensions:**
  - Foundational Compliance: 93 / 100
  - Developer Experience & Jentic Compatibility: 72 / 100
  - AI-Readiness & Agent Experience: 45 / 100
  - Agent Usability: 94 / 100
  - Security: 60 / 100
  - AI Discoverability: 80 / 100
- **View full report:** https://jentic.com/apis/meetzi.co/meetzi/scorecard
- **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/
- **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview

### Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

- **Score your own API:** https://jentic.com/scorecard.md
- **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md

```sh
npx @jentic/api-scorecard-cli score <openapi-url>
```

## Why Jentic

- **Setup:** Wiring Meetzi by hand means generating a key under Integrations, sending it as a bearer token on every /v1 call, and standing up a callback receiver for subscriptions that deliver once with no retry. Through Jentic you install once, import Meetzi from the API Directory, store the key once, and your agent calls it.
- **Permission scoping:** Meetzi passes the booking page as a query or body field rather than in the URL path, so rules bound which operations your agent may call, not which booking page it reads. You choose the operations it may call, so webhook creation and subscription deactivation are not included unless you add them.
- **Credential handling:** Your Meetzi API key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'list new bookings' or 'subscribe to cancelled meetings', and Jentic returns the matching Meetzi operation with its input schema, including booking_page_id and limit, so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Calendly API** — Scheduling platform with event types, scheduled events, invitees, and webhook subscriptions
- **Acuity Scheduling API** — Appointment scheduling with availability, appointment booking, and client records
- **Cronofy API** — Calendar connectivity and availability across Google, Outlook, and iCloud calendars

## FAQ

### What authentication does the Meetzi Booking Automation API use?

Per its OpenAPI spec, the Meetzi API authenticates with HTTP bearer auth: you send a Meetzi API key, generated under Integrations then Zapier, in the Authorization header as a bearer token. The same key works for Zapier and custom server integrations. Through Jentic the key is stored encrypted by your own Jentic One instance and injected at call time, so it never enters the agent's context.

### Can I get notified when a guest cancels a Meetzi booking?

Yes. POST `/v1/subscriptions` with trigger_type booking_cancelled and a target_url, and Meetzi posts the cancelled booking object to that URL. Set booking_page_id to one owned page, or leave it null to cover all owned pages. Deliveries are attempted once with no signature, and a 410 response from your receiver prompts Meetzi to deactivate the subscription.

### What are the rate limits for the Meetzi Booking Automation API?

The OpenAPI spec states that no request quota or rate-limit headers are specified. The trigger endpoints accept a limit of up to 500 recent records per call with no cursor pagination. Check the Meetzi documentation at https://docs.meetzi.co for any current limits.

### Is there a Meetzi MCP server?

You don't need an MCP server to give your agent Meetzi. Jentic connects it directly from the API Directory: import it, store your API key once, and your agent calls the booking operations it needs on demand without loading another server's tool definitions into its context.

### How do I read new bookings for one booking page through Jentic?

Search Jentic for 'list new Meetzi bookings', load the GET `/v1/triggers/new-bookings` operation, and execute it with the booking_page_id from GET `/v1/booking-pages` and an optional limit. Each record returns the guest, the start and end time, and the meeting option. To run it on your own infrastructure, install Jentic One from its GitHub repo.

### Can I limit what my agent is allowed to do with the Meetzi API?

Yes. Write a rule that allows only the three booking trigger reads and the booking-page list, and the agent can report on bookings without being able to register or deactivate webhooks. Every call it makes is logged, so you can review exactly which booking reads it ran.