Developers
The developer page without the vaporware.
Two facts up front: there is no public REST API today, and no outbound webhooks. What does exist: an MCP server AI tools call directly, and a booking widget on npm. Here is what you can actually do, and where to push if you need more.
An MCP server your AI tools can call
https://buildoutschedule.com/api/mcp speaks the Model Context Protocol. Claude, Cursor, and anything else that speaks MCP can list a workspace’s event types and read live availability with no token, and book, reschedule, or cancel with a bearer token from /settings/mcp.
A booking widget on npm
npm install @buildoutstudios/schedule gets a React <BookingWidget /> plus a plain script embed. It renders your hosted booking page and fires a callback when a visitor books — no API keys, no backend.
OAuth integrations that work
Google Calendar, Microsoft, Zoom, Stripe, Slack, and Twilio connect per workspace with tokens encrypted at rest. If your team’s stack is those six, no code required.
Hosted pages you can point at
Schedule Pages and Rep Cards live on your own subdomain or domain with one CNAME. Most embed-scheduling-on-my-site cases are a link or a frame to those pages.
Tokenized public actions
Cancel and reschedule run on scoped, single-booking tokens — attendees act without accounts, and a token exposes exactly one booking.
Automation without endpoints
The workflow engine fires email and SMS on booking events, and Slack posts keep systems-of-record humans in the loop. Not an API — but it covers a lot of what people wire APIs up to do.
Need the API to exist?
The internal service layer is built the way a public API wants to be exposed — the open question is which endpoints earn their keep first. Email chase@tnvex.com with what you would build. Concrete use cases from real workspaces set the build order.
Watching for updates? The changelog is where an API launch would land first.
Related
Use the product while the API earns its page.
Free forever plan. No credit card.