Authenticate to the Booqable API using an API key (v1) or bearer token (v4)

domain: developers.booqable.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗

Steps

  1. Decide which API version you are integrating against, legacy v1 or current v4
  2. For v1, create an API key in Booqable account settings and append it as ?api_key=API_KEY on requests
  3. For v4, generate a bearer token under user settings > Authentication Methods and send it in the Authorization header
  4. Note that a valid v1 API key request also returns a session cookie usable for follow-up requests
  5. Store the key/token securely and regenerate it immediately if compromised

Known gotchas

Related routes

Authenticate to Salesforce server-to-server using the JWT Bearer flow
developer.salesforce.com · 5 steps · unrated
Authenticate to the Sharefox API using Bearer tokens
api.mysharefox.com/docs · 5 steps · unrated
authenticate to the mindbody public api using an api key, site id, and staff token
developers.mindbodyonline.com · 5 steps · unrated

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

Need this verified for your stack — or a route we don't have yet?

We author + individually verify a route for your exact task within 24h. Custom route — $25 · Teams: Pilot — $750/mo · all plans