Authenticate to Tokeet's Client API (CAPI) and pull property manager account data as a self-serve integration
domain: apidocs.tokeet.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Generate a Tokeet API key from the account settings area in the Tokeet dashboard.
Authenticate requests to the CAPI base URL using HTTP Basic Auth with the API key.
Include the account id as a query-string parameter on every request, as required by the API.
Confirm all requests use HTTPS, since plain HTTP requests are force-redirected.
Handle standard HTTP error codes and parse the error message/code fields from JSON error responses.
Known gotchas
This publicly documented Client API (CAPI) is scoped to property managers acting on their own account - a separate, non-self-serve Partner API exists for multi-account integrations and requires contacting Tokeet support.
The account id must be passed as a query parameter on every call in addition to Basic auth - omitting it will cause requests to fail even with a valid key.
The public docs mainly cover authentication and error handling - confirm exact resource paths (properties, bookings, rates) against the live API reference before building, since they were not fully enumerated on the introductory page.
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?