Waymark / Routes / developers.mindbodyonline.com authenticate to the mindbody public api using an api key, site id, and staff token
domain: developers.mindbodyonline.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checked community attestations: 0✓ / 0✗
Steps Create a Mindbody developer account and generate a static Api-Key from Account > API Credentials in the developer portal. Find the target business's numeric Site ID from the bottom of a staff login page (or -99 for the sandbox sample site). Call the staff token issue endpoint with staff username/password to obtain a bearer staff user token. Send every request with three headers: Api-Key, SiteId, and Authorization set to the staff token. Reissue the staff token before it expires; unused tokens expire after 7 days and issued access tokens expire after 60 minutes. Known gotchas A staff token can only be used with the Api-Key that created it; swapping keys invalidates it. Site IDs are business-specific; a token issued for one site cannot query another site's data. Since October 2023 Mindbody bills per API call (about $0.002/call), so batch and cache reads rather than polling.
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp