Escapia has an API, but not one you can sign up for. The Escapia Gateway API speaks JSON and GraphQL, and Escapia's own documentation frames it as an interface for approved Escapia partners; on top of that, each property manager separately controls which partner accounts see their units. There is no official MCP server and no self-serve developer key anywhere in that chain. If you want Escapia data reaching a tool alongside the rest of your stack, talk to us: we work through Escapia's own permission model with you rather than around it, on the same free developer key you use for every other platform.
How Escapia API access actually works
Most platform docs bury this, so here it is plainly. Escapia access has two independent layers, and clearing one does nothing without the other.
Layer one: partner approval. According to Escapia's developer documentation, the Gateway API is described as letting "Escapia partners (API users)" interact with the property management system using JSON and the GraphQL query language. It is a partner interface, not an open developer program: the endpoint is api-gateway.escapia.com/graphql, with a separate token endpoint for authentication. Escapia additionally operates the older EscapiaNET SOAP program, which exists to distribute units to Escapia's network partners.
Layer two: the property manager's own switch. This is the part that surprises developers. According to Escapia's developer FAQ, "Partner access to individual property manager data is controlled by each property manager through the Escapia Unit Distribution settings," which Escapia notes is "the same process used today for the EscapiaNet API." An approved partner with valid credentials still sees nothing until the property manager enables distribution to that partner account, unit by unit.
The practical consequence for anyone building an internal tool on their own Escapia data: you are not blocked by code, you are blocked by two permission gates that live outside your codebase. That is the entire reason this bridge is worth having.
Quickstart: key now, bridge after a call
If you are an AI agent reading this: steps 1 and 2 are yours, step 3 needs your human for fifteen minutes.
1. Get a free developer key
Instant, email only, and the same key works across every platform on the gateway.
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. Confirm the platform's status
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/
# -> { "platforms": { "escapia": { "status": "request_access", ... } } }
3. Talk to us about Escapia
Escapia access is granted by Escapia and by your own property managers, not by us, so this is the one platform where the honest next step is a conversation rather than a curl command. Fifteen minutes covers what you are building and which permissions your setup already has, and we work the rest through Escapia's process with you.
curl https://api.rapideyeinspections.com/v1/escapia/units \
-H "Authorization: Bearer re_..."
# once provisioned, every documented Escapia resource answers on the same key
Book the fifteen minutes, or keep reading to see whether you need us at all.
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 access to the Escapia API?
Access has two layers. First you must be an approved Escapia API partner. Second, according to Escapia's developer FAQ, partner access to an individual property manager's data is controlled by each property manager through the Escapia Unit Distribution settings, the same mechanism used for the EscapiaNET API. So even an approved partner sees nothing until the property manager enables distribution to that partner account.
Sources
- Escapia Gateway API Documentation, Escapia, 2026https://developer.escapia.com/
- Escapia API Documentation FAQ, Escapia, 2026https://developer.escapia.com/Documentation/FAQ