API Endpoints
The Meet.bot REST API gives you everything you need to list scheduling pages, check availability, and book meetings programmatically.
| Method | Endpoint | Description |
|---|---|---|
GET |
/v1/pages |
List all your scheduling pages |
GET |
/v1/info |
Get detailed page information |
GET |
/v1/slots |
Get available booking time slots |
POST |
/v1/book |
Book a meeting |
POST |
/v1/page-create |
Create a new scheduling page |
GET |
/v1/page-config |
Get page configuration |
See the full interactive API documentation for request parameters, response schemas, and examples.
Authentication
All API requests require a Bearer token in the Authorization header. You can generate your token at meet.bot/automation.
curl -H "Authorization: Bearer YOUR_TOKEN" \
https://meet.bot/v1/pages
Include this header with every request. Requests without a valid token will receive a 401 Unauthorized response.
Quick Start
This Python example shows the core workflow: retrieve available time slots for a scheduling page, then book a meeting in the first available slot.
import requests
API_TOKEN = "YOUR_TOKEN"
BASE_URL = "https://meet.bot/v1"
HEADERS = {"Authorization": f"Bearer {API_TOKEN}"}
# 1. List your scheduling pages
pages = requests.get(f"{BASE_URL}/pages", headers=HEADERS).json()
page_slug = pages[0]["slug"]
# 2. Get available time slots
slots = requests.get(
f"{BASE_URL}/slots",
headers=HEADERS,
params={"page": page_slug}
).json()
# 3. Pick a slot and book the meeting
slot = slots[0]
booking = requests.post(
f"{BASE_URL}/book",
headers=HEADERS,
json={
"page": page_slug,
"slot": slot["slot"],
"name": "Jane Smith",
"email": "jane@example.com"
}
).json()
print(f"Meeting booked: {booking['meeting_url']}")
SDKs & Tools
Use the Meet.bot API directly or through the tools and specifications we provide.
REST API
Full API access to scheduling pages, time slots, and booking. Works with any language or HTTP client.
OpenAPI Spec
Machine-readable API specification. Generate client libraries in any language or import into tools like Postman.
MCP Server
Model Context Protocol server for AI agents. Let LLMs check availability and book meetings through tool calling.
n8n Node
Native Meet.bot node for n8n workflow automation. Connect scheduling to your existing automation pipelines.
Webhooks
Real-time partner event notifications. Receive JWT-signed payloads for bookings and connection events.
Getting Started
Go from sign-up to your first API call in minutes.
Create a free account
Sign up at meet.bot/signup and connect your calendar. No credit card required.
Get your API token
Go to meet.bot/automation to generate your personal API token for authenticating requests.
Make your first API call
Use the token to call GET /v1/pages and list your scheduling pages. You are ready to build.
Frequently Asked Questions
The Meet.bot API uses Bearer token authentication. Include your API token in the Authorization header of every request: Authorization: Bearer YOUR_TOKEN. You can get your token at meet.bot/automation.
Yes, standard rate limits apply to all API endpoints. The limits are generous enough for typical scheduling automation and AI agent use cases. If you need higher limits, contact us.
All API responses are returned in JSON format. Request bodies for POST endpoints should also be sent as JSON with the Content-Type: application/json header.
Yes. Use the POST /v1/page-create endpoint to create new scheduling pages programmatically. You can also retrieve page configuration with GET /v1/page-config.
Meet.bot sends partner webhooks with JWT-signed payloads. When events like bookings or partner connections occur, a POST request is sent to your configured webhook URL. You verify the JWT signature using your shared secret to ensure the payload is authentic.
Meet.bot provides an OpenAPI specification at /api/yaml/ that you can use to generate client libraries in any language. There are also community integrations available for platforms like n8n.
Pay Per Meeting, Not Per User
Your whole team can use Meet.bot and you only pay when meetings happen. No per-seat fees for API access.
