Meet.bot Booking Page API

Name: Meet.bot Booking Page API
Brand: Meet.bot Booking Page API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentProductivityCalendar Schedulingbearer8 EndpointsREST

For 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.

Install Jentic One Beta

Connect the Meet.bot Booking Page API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Meet.bot Booking Page API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Meet.bot Booking Page API.

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

GET STARTED

Start building with Meet.bot Booking Page API

Explore with Jentic

View OpenAPI Document

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.

Use Cases

Patterns agents use Meet.bot Booking Page API for, with concrete tasks.

★ 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.

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.

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.

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.

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

8 endpoints — jentic publishes the only available openapi specification for meet.

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

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

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Meet.bot bearer tokens are stored encrypted in the Jentic vault and injected as Authorization headers at execution time. The raw token never enters the agent's context.

Intent-based discovery

Agents search by intent (e.g. 'book a meeting slot') and Jentic returns the matching Meet.bot operation along with the schema for slot ids and invitee fields.

Time to first call

Direct Meet.bot integration: half a day for auth, slot retrieval, and booking confirmation. Through Jentic: under 30 minutes — search, load schema, execute.

FAQs

Specific to using Meet.bot Booking Page API through Jentic.

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 at https://app.jentic.com/sign-up.

What authentication does the Meet.bot Booking Page API use?

It uses HTTP Bearer authentication: callers send an Authorization: Bearer <token> 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.

Meet.bot Booking Page API

Connect the Meet.bot Booking Page API to your agent

Capabilities

Start building with Meet.bot Booking Page API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs