The Sixto API: the same actions and permissions your team uses
The Sixto API exposes the same actions the app uses, such as tasks, records, reports and messages, through keys that only have the scopes you give them. Every call is recorded in that key's activity log. A key can check what it is allowed to do and who it is. Sensitive actions wait for a person to confirm them.
Available. A versioned REST API with scoped keys covers reservations, guests, tasks, finance, check-in, locks, channels and more.
Your tools, scoped access
API keys only get the permissions you choose
What it does
Know what moves, and what stays put
Arrows describe data direction relative to Sixto.
Broad coverage
Tasks, reservations, guests, reviews, messages, check-in, compliance, locks, channels, e-invoices, bank and ledger, market benchmarks, search and settings.
Scoped keys from one permission catalog
Keys draw from the same permission catalog as people. To change permissions, an Owner creates a replacement key and revokes the old one. Revocation takes effect on the next call.
Self-describing
Ask the API who you are and what you may do (whoami and capabilities), including each route's required permissions.
Safe retries and an activity log
Each write documents its retry identity, such as external_id or an Idempotency-Key header, and returns 409 if the same identity is reused with different content. Every request has an ID and appears in the activity log.
Fair limits
Each key has its own allowance, 600 requests a minute by default, so one busy key never slows another. GET /api/v1/capabilities reports the current value.
Prefer an AI app? Use MCP
Besides the REST API, Sixto has an MCP server for AI apps, signed in with OAuth and off until an Owner or Manager turns it on, plus a public read-only Docs MCP.
- Server address
https://sixto.app/mcp- Docs MCP
https://sixto.app/mcp/docsPublic and read only. It searches Sixto's documentation and never sees your organization's data.
How it works
- 01
An Owner creates a key under Settings and ticks the permissions it needs. The key is shown once.
- 02
Send it as a Bearer token. Call whoami and capabilities to see what the key can do.
- 03
Read or write through the endpoints. Writes run the same checks as the app.
- 04
Watch calls in the API activity view, and revoke a key whenever you want.
What syncs
Common questions
Is there a developer guide?
Yes. The OpenAPI 3.1 reference is at /api/v1/openapi.json and the client guide is at /api/v1/guide.json. Each operation shows x-contract-status: complete means a reviewed contract, unsupported means the route stays available but is outside the supported client surface. A read-only docs server is at /mcp/docs.
What does a key act as?
A key acts for the organization, within its own permissions. It has no property list of its own and does not inherit the property limits of the person who created it. When Sixto forwards a person's request with a Sixto-On-Behalf-Of delegation, that person's current property and permission limits also apply.
How do I change a key's permissions?
Create a replacement key with the permissions you want, switch your tool to it, then revoke the old key. Existing keys cannot be edited. A revoked key is refused on its next call.
What do 422 and 429 mean?
422 means validation failed: read the errors object by field, correct the input and send again. 429 means the key reached its limit: wait the number of seconds in the Retry-After header, then retry with backoff. Keep the X-Request-Id to find the call in the activity log.
Can a key unlock a door?
No. Remote unlock is never available through the API.
Is the API versioned?
Yes, it lives under /api/v1.

