API & MCP overview

AutoSync exposes one API across Mindbody, Booker, and HighLevel calendars. Point an AI agent or your own code at a single base URL with a single bearer token, and AutoSync handles the platform routing, calendar mapping, contact lookup, and dual-write.

Two ways to call it

REST — plain HTTP at https://autosync.io/api/v1/*. Build any integration in any language.
MCP — the Model Context Protocol server at https://autosync.io/mcp, so AI agents (Claude, ChatGPT, Cursor) can book, reschedule, and look things up conversationally. Same bearer token as REST. See Connect an AI agent.

Base URLs

Environment	Base URL
Production	`https://autosync.io`
Development (testing)	`https://dev.autosync.io`

Supported platforms

Every endpoint is namespaced by platform: mindbody, booker, or ghl. The platform in the URL must match the one configured on your location — a mismatch returns 403 platform.mismatch. Restore/POW is not exposed through the public API and returns 501.

Discover the surface without a key

The catalog and docs endpoints need no authentication, so you can explore before minting a key:

curl https://autosync.io/api/v1/

Interactive docs (Scalar, with try-it-out): autosync.io/api/v1/docs
OpenAPI 3.1 spec (paste into ChatGPT or an SDK generator): autosync.io/api/v1/openapi.json
Endpoint catalog: autosync.io/api/v1/

The interactive docs are generated straight from the API and are always the canonical, up-to-the-minute reference for exact request/response shapes. These pages explain the concepts and the how-to; the explorer is the contract.

Getting access

Using the API requires API access to be enabled on your account (a paid add-on you turn on from the API & AI Access page inside your AutoSync HighLevel menu). Next: mint a key and authenticate →

Last updated July 2026