BusyBoard API

Read availability, find mutual free time, and list people and groups — programmatically.

Overview

The BusyBoard REST API exposes the same privacy model as the app: you get full detail for your own busy blocks, and free/busy only for everyone else — never event titles, attendees, or descriptions. The full machine-readable spec is published as OpenAPI 3.1 (/openapi.yaml).

  • Base URL: https://busyboard.app/api/v1
  • Auth: Bearer API key (bb_live_…), created in Settings → API & Integrations
  • API access requires a Pro plan
  • Rate limit: 100 requests/minute; every response carries an X-Request-Id
  • List endpoints are paginated (cursor/limit)

Authentication

curl https://busyboard.app/api/v1/me \
  -H "Authorization: Bearer bb_live_your_key_here"

Endpoints

MethodPathDescription
GET/meCurrent user profile, plan, and timezone
GET/peoplePeople you can see availability for (org members + external connections)
GET/groupsYour groups and their members
GET/availabilityBusy blocks for one or more users in a date range
GET/availability/summaryPer-day free/busy summary
POST/find-timeFind mutual free slots across multiple people
GET/calendarsYour connected calendar accounts and sync status
GET/working-hoursYour working hours configuration

Request/response schemas, error codes, and examples are in the OpenAPI spec.

MCP server for AI agents

BusyBoard ships an MCP (Model Context Protocol) server, @busyboard/mcp, that wraps this API with five tools — get_my_schedule, get_my_availability, get_person_availability, list_my_people, and find_mutual_time — so AI assistants like Claude can check availability and find meeting times on your behalf. There is also a CLI (bb) with the same capabilities. Both authenticate with the same API keys.

Getting started

  1. Create a BusyBoard account and connect a Google or Outlook calendar
  2. Upgrade to Pro (pricing)
  3. Create an API key in Settings → API & Integrations
  4. Call GET /api/v1/me to verify