canonical: https://jentic.com/apis/meet.bot/meet-bot # Meet.bot Booking Page API Jentic publishes the only available OpenAPI specification for Meet.bot Booking Page API, keeping it validated and agent-ready. Meet.bot is a scheduling platform that lets users publish booking pages and accept meeting bookings from invitees. The API exposes 8 endpoints across booking, configuration, and pages, including operations to list booking pages, create new ones, configure them, fetch available slots, and book a slot on behalf of an invitee. Use it when an agent needs to schedule meetings, expose a booking page in another product, or read availability before sending an invite. ## For AI agents List, create, and configure Meet.bot booking pages and book meeting slots so an agent can schedule on behalf of a user without opening the Meet.bot UI. ## Scope Does not handle video conferencing, calendar conflict detection across other calendars, or payment collection - use for booking-page management and meeting bookings only. ## Capabilities - List all booking pages owned by the authenticated user - Create a new booking page with title, duration, and availability rules - Update the configuration of an existing booking page including buffer times - Fetch the available slots for a given booking page and date range - Book a specific slot on a booking page on behalf of an invitee with name and email - Retrieve the public info for a booking page so it can be embedded elsewhere ## Use cases ### Embedded Booking in a Sales Workflow Surface a salesperson's Meet.bot availability inside a CRM or outbound email tool so a prospect can pick a slot without leaving the message. The `/v1/slots` and `/v1/book` endpoints give a clean read-then-write flow that an agent can drive in two calls. Sales teams use this to remove the back-and-forth that normally drags discovery scheduling into a multi-day thread. Example prompt: Call `/v1/slots` for the booking page id sales-discovery between dates 2026-06-12 and 2026-06-19, then post `/v1/book` with the chosen slot and invitee email to confirm the meeting. ### Programmatic Booking Page Provisioning Spin up booking pages on demand for new hires, events, or office hours rather than configuring each one by hand in the Meet.bot UI. The `/v1/page-create` endpoint accepts the page configuration as a single payload, so an HR or community-ops agent can stamp out dozens of consistent booking pages from a template. This shortens onboarding time when a new cohort joins. Example prompt: Create a booking page titled 1:1 with Sam with duration 30 minutes and weekday business-hours availability by calling `/v1/page-create.` ### Concierge Scheduling Agent Hand a personal scheduling assistant the ability to negotiate a meeting time entirely on its own: it inspects available slots, proposes options to the invitee, and confirms the booking once a time is chosen. With Meet.bot the agent only needs three operations - list pages, fetch slots, book - and Jentic handles the credential injection. The result is a scheduling experience that feels human without a human in the loop. Example prompt: Inspect `/v1/pages` to find my main booking page, fetch `/v1/slots` for next week, propose three options to the invitee in chat, and call `/v1/book` once they pick one. ### Availability Snapshot for Reporting Pull a snapshot of upcoming availability across all of a user's booking pages to feed an internal capacity dashboard. Combining `/v1/pages` with `/v1/slots` lets a reporting agent show how many open slots exist per page over the next two weeks. Operations teams use this to balance load between team members or close pages that are oversubscribed. Example prompt: List all pages with `/v1/pages` then call `/v1/slots` for each over a 14-day window and return a count of open slots per page. ## Key endpoints | Method | Path | Description | | --- | --- | --- | | GET | `/v1/pages` | List booking pages owned by the user | | POST | `/v1/page-create` | Create a new booking page | | POST | `/v1/page-config` | Update the configuration of a booking page | | GET | `/v1/slots` | Fetch available slots for a booking page | | POST | `/v1/book` | Book a slot on behalf of an invitee | | GET | `/v1/info` | Retrieve public info for a booking page | ## Key resources - **Pages** — List, create, and read booking pages owned by the authenticated user - **Configuration** — Update the settings of a booking page including duration, buffer times, and availability rules - **Slots** — Fetch available slots for a given booking page and date range - **Booking** — Book a chosen slot on behalf of an invitee with their name and email ## Why Jentic - **Setup:** Wiring the Meet.bot Booking Page API by hand means handling bearer token auth, pointing at the meet.bot host, and mapping the booking-page and slot operations yourself. Through Jentic you install once, import the Meet.bot Booking Page API from the API Directory, store the token once, and your agent calls it. - **Permission scoping:** Meet.bot's page configuration and booking details travel in the request body or query rather than a resource id in the URL path, so you limit the agent to the operations it needs, such as listing pages and slots or booking a meeting. It calls only the operations you allow, so page creation is not included unless you add it. - **Credential handling:** Your Meet.bot bearer token is stored once, encrypted, by your own Jentic One instance and injected as the Authorization header at execution time. It never enters the agent's prompt, logs, or context. - **Discovery method:** Agents search Jentic by intent such as 'book a meeting slot', and Jentic returns the matching Meet.bot operation with the schema for slot ids and invitee fields so the agent calls the right endpoint without browsing the reference docs. ## Related APIs - **Calendly API** — Calendly is a more established booking platform with deeper integrations and a richer event-type model. - **Acuity Scheduling API** — Acuity targets service businesses with appointment intake forms and packages. - **Zoom Meetings API** — Zoom provides the video conferencing room for the meeting that Meet.bot books. - **Google Calendar API** — Google Calendar is where the booked meeting actually lands on the host's schedule. ## FAQ ### Why is there no official OpenAPI spec for Meet.bot Booking Page API? Meet.bot does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Meet.bot Booking Page API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer. ### What authentication does the Meet.bot Booking Page API use? It uses HTTP Bearer authentication: callers send an Authorization: Bearer header. Through Jentic the token is stored encrypted in the vault and injected at execution time so the agent does not see the raw value. ### Can I book a meeting slot programmatically? Yes. Call `/v1/slots` first with the booking page id and a date range to get open slots, then POST to `/v1/book` with the chosen slot identifier and the invitee's name and email to confirm the booking. ### What are the rate limits for the Meet.bot Booking Page API? Meet.bot does not publish a numerical rate limit. Treat list and slot-fetch calls as cacheable and avoid bursting `/v1/book` calls in parallel - if you receive a 429, back off exponentially before retrying through Jentic. ### How do I create a booking page through Jentic? Search Jentic for create a Meet.bot booking page, load the schema for `/v1/page-create`, and execute with the title, duration, and availability rules. Jentic returns the new page id and public URL ready to share with invitees. ### Can I configure buffer times on a booking page? Yes. The `/v1/page-config` endpoint accepts buffer-before and buffer-after settings alongside duration and working hours, so an agent can shape availability without opening the Meet.bot dashboard. ### Can I limit what my agent is allowed to do with the Meet.bot Booking Page API? Yes. Because you run Jentic One yourself, your own rules decide which Meet.bot operations and credentials the agent can use, so it calls only the endpoints you allow. You can grant read-and-book access with listing pages (`/v1/pages`), fetching slots (`/v1/slots`), and booking (`/v1/book`) while withholding page creation (`/v1/page-create`) and configuration changes (`/v1/page-config`). Since page and booking details travel in the request body or query rather than a resource id in the path, you scope the agent at the operation level and it cannot reach anything you have not enabled.