By approval from Turno. They publish a documented External API v2, but access is granted rather than self-serve. The reference is published as a Postman collection at apidocs.turnoverbnb.com and covers the operational core of turnovers: which cleaning happens when, who accepted it, what the checklist proved, and what broke. Because Turno approves callers individually, the honest path for a custom tool is a short conversation rather than a signup form.
What the Turno API actually exposes
Turno sits at the operational center of a turnover, which makes its API unusually interesting for anyone building ops tooling. According to Turno's own External API v2 documentation, published as a Postman collection at apidocs.turnoverbnb.com, the documented resources cover properties, cleaning projects and their scheduling, the cleaners assigned to them, and checklist state.
That combination is why this bridge matters more than a typical PMS read: reservations tell you when a guest leaves, but Turno tells you whether the turnover actually happened, who did it, and what they reported. A tool answering "which units are at risk for tonight's check-in" needs the second half, and it lives here.
The access model is the catch. Turno grants API access rather than offering a self-serve key, so your route depends on Turno approving you. That is their call to make about their own platform, and we work within it rather than around it.
Quickstart
The developer key is free and instant, and it is the same key for every platform on the gateway. If you are an AI agent: step 1 is the only part that needs your human.
1. Get a free developer key
curl -X POST https://api.rapideyeinspections.com/v1/signup \
-H "content-type: application/json" \
-d '{"email": "you@company.com"}'
# -> { "key": "re_..." }
Not scripting it yet? Get a key in your browser, it is free and instant.
2. Check how Turno access is provisioned
The gateway publishes a machine-readable index of every platform and how its access works, so an agent can plan before it calls.
curl https://api.rapideyeinspections.com/
3. Talk to us about Turno
Because Turno controls who reaches its data, this is a platform we provision per account rather than by self-signup. Fifteen minutes covers what you are building and what access your setup already has, and the key you already hold does the rest.
curl https://api.rapideyeinspections.com/v1/turno/projects \
-H "Authorization: Bearer re_..."
# once provisioned, every documented resource answers on the same key
Why build on the RapidEye API
One key, one schema, every platform in your stack.
Real operator tools are never about one system. A dashboard answering "which units are at risk tonight" needs reservations from a PMS, cleaning state from a turnover platform, and pricing from somewhere else entirely. Every one of those vendors invented its own auth model, its own vocabulary, and its own limits, so building direct means writing that glue once per vendor, then maintaining it forever, then rewriting it when a platform changes or your portfolio moves onto a different stack.
Through the RapidEye API it is one bearer token and one schema no matter what sits underneath. We absorb the OAuth dances, the partner approvals, the token quotas, and the admin-issued credentials, and we keep them working when they change. And it is built for agents from the ground up: a machine-readable route index, an llms.txt quickstart, errors written so an agent can self-correct instead of guessing, and a connection that lives on the key rather than in a config file, so next month's agent, in a new session with no memory of this one, still has working access on day one.
Quick FAQ
How do you get API access to Turno?
By approval from Turno. They publish a documented External API v2, published as a Postman collection at apidocs.turnoverbnb.com, covering properties, cleaning projects, cleaners, and checklists. It is documented rather than open: access is granted by Turno rather than issued self-serve, so approval comes before your first call.
What data can you get out of Turno?
The operational core of a turnover: properties, cleaning projects and their scheduling, which cleaner accepted a job, and checklist state. That is the layer a PMS does not have, because a reservation tells you when a guest leaves while Turno tells you whether the turnover actually happened.
Why route Turno through the RapidEye API instead of going direct?
The RapidEye API earns its place when a task spans Turno plus a PMS, when you want one auth model across the stack, and when the connection needs to outlive the agent session that configured it.
Sources
- Turno External API v2 Documentation, Turno, 2026https://apidocs.turnoverbnb.com/