API & Integrations

API & Integrations

FlowCaptain works out of the box — no external tools or programming required. For custom integrations, a full API is available.

When do you need the API?

• Own voice bot platform — You already run a voice bot and want to connect FlowCaptain's appointment logic
• Chat integration — You want to add appointment booking to your website chat or messenger
• Automation — You want to check or book appointments from other systems

Integration Methods

Autopilot — A single endpoint for full conversation management. FlowCaptain handles greeting, appointment search, booking, and farewell. Your system just forwards messages.

Individual Endpoints (REST) — Separate endpoints for each action (check availability, book, cancel, reschedule). You control the conversation flow.

MCP (Model Context Protocol) — A single endpoint where your system automatically discovers all available tools.

Base URL

https://api.flowcaptain.com

Interactive API documentation is available at api.flowcaptain.com/docs.

Authentication

All API requests require an API key as Bearer token (created in the workspace Settings under API Keys):

Authorization: Bearer sk_live_your_api_key

Every request also needs your calendar ID. Autopilot and REST endpoints require calendarId as the first field in the JSON body; MCP requires it as a query parameter on the URL. You find your calendar ID pre-filled in every example under Dashboard → Calendar → API → Integration Guide. If your platform wraps the request body in an envelope (e.g. Retell's args object), pass calendarId as a URL query parameter instead — ?calendarId=YOUR_CALENDAR_ID — because the API only reads it from the top-level body, the query string, or the route params, never from a nested args object.