Every rental platform, one API
Reach vacation rental platform data without becoming a certified partner of each one. The RapidEye API exposes each platform as a hosted connector: we handle whatever approval, OAuth dance, or admin-issued credential that platform demands, and your agent or custom-built tool calls one consistent surface. Connectors are enabled per account in a 15-minute call.
# the base URL, once API=https://api.rapideyeinspections.com # 1. discover what the API offers (no key needed) curl $API/ curl $API/connectors # 2. call the platform you run curl $API/connectors/hostaway/listings # 3. a connector not yet enabled for your account # answers with exactly what to do next, including # the booking link that turns it on.
- Built for agents, not just peopleEvery surface is documented in machine-readable form at the API root, plus an llms.txt written as an agent quickstart. A gated connector answers with the exact next step, so an agent can hand the booking link to its human instead of guessing.
- One auth model instead of a dozenOAuth client credentials, basic auth, header keys: each platform demands something different. The connector absorbs that once it is enabled for your account. Your code calls one consistent surface.
- Enable once, inherit foreverThe connection lives on your account, not in a config file. Next month's agent, in a new session with no memory, still has working access.
Looking for inspection findings rather than platform data? This page covers the connectors: one API surface that reaches the platforms you already run. If you want to send turnover photos or video and get damage findings back, that is RapidEye's own inspection engine: see the RapidEye API.
Platforms
Available means RapidEye has built and operated this connector before, so enabling it for your account is a 15-minute conversation rather than engineering work. Request access means that platform controls its data at the source (partner approval, distribution permissions, admin-issued credentials), so we provision it per account directly with you. Either way, the call is where it turns on.
Hostaway
AvailableOAuth client credentials minted and refreshed for you. Listings, reservations, tasks, calendar.
OwnerRez
AvailableBookings, properties, guests and owners. Note the two-accounts-per-IP token limit.
PriceLabs
AvailablePricing and listing data, joinable against whatever PMS you are on.
Guesty
Request accessFive access tokens per client ID per 24 hours: token caching is not optional.
Hospitable
Request accessFirst official MCP in the industry, and write-capable. We say use theirs.
Escapia
Request accessPartner-gated GraphQL gateway plus per-property-manager permission.
Track
Request access90-plus resource collections. Mirrors the PMS operational core, not a listings feed.
Streamline
Request accessPropertyCare work orders: the field-ops layer most PMS APIs stop short of.
Turno
Request accessDocumented External API v2, access granted rather than self-serve.
TIDY
Request accessLive first-party MCP, write-capable. Cleaning state to join against a PMS.
Cloudbeds
Request accessSelf-serve keys with scopes chosen at creation. Rare in hospitality.
Mews
Request accessFive-state resource model plus a public demo environment to build against.
Lodgify
Request accessPublic API key carries write scope you cannot turn off. MCP is waitlisted.
Hostfully
Request accessA "lead" is the booking, not a sales prospect. Orders hold the money.
Tokeet
Request accessSelf-serve key, documented CAPI, and zero agent tooling anywhere.
iGMS
Request accessDocumented API, no MCP, and no Zapier app despite what blogs claim.
CiiRUS
Request accessIn-platform AI, but nothing for outside agents. CiiRUS-API is the route.
RentalReady
Request accessShipped an official MCP in June 2026, among the first to do so.
Your platform
AskNot listed? Tell us which one your build needs and we will look at it.
Real tools span platforms
A revenue dashboard needs bookings and pricing. An owner report needs reservations and cleaning status. No single platform's API can answer a question that crosses two systems; one API surface can.
Errors an agent can act on
A raw 403 tells an agent nothing. Our errors name the cause and the fix, including the exact next call, so an agent can self-correct instead of guessing or giving up.
State that outlives a session
Agents start every session with no memory. The connection lives on your account, so the next agent, in a new chat, with a different model, still has working access on day one.
When you should not use this
If your tool only ever touches one platform, and that platform has a good self-serve API you already hold credentials for, call it directly. Hostaway, PriceLabs, and OwnerRez all publish real documentation, and adding a hop through us buys you nothing on a single-platform task. We would rather say that plainly than win a request you did not need us for.
Where the gateway genuinely earns its place: platforms that gate access behind partner approval, tasks that span more than one system, and any agent-built tool that has to keep working long after the session that wrote it. This is the platform-data half of what we publish. The inspection engine itself, where you send photos or video and get back damage findings, is a separate product with its own docs at the RapidEye inspection API.
Questions
How do you connect a vacation rental platform to an AI agent?
The RapidEye API exposes each platform as a hosted connector, enabled per account, and the gateway handles that platform's authentication model, whether that is OAuth client credentials, basic auth, or a header key. The catalogue is machine-readable, so an agent can discover what exists without a human in the loop.
Is it free?
Trying it costs nothing: the demo tier takes an email address per submission, no key, no card. Connectors are provisioned per account in a short call with the RapidEye founders, because most platforms control access to their data at the source. Production integrations run on the Partner API with a key issued by RapidEye.
Does RapidEye store my platform credentials?
When a connector is enabled for your account, yes, encrypted: that is what lets every future agent session inherit a working connection instead of reconfiguring it. Credentials are sealed before storage and only decrypted in memory to sign an outbound request.
Why would an AI agent use this instead of a platform's own API?
For a task touching one platform with a good self-serve API, it should not; the direct path is simpler and we say so on every page. The gateway earns its place when authentication is the hard part, when a task spans multiple platforms and you want one schema, when errors need to be readable enough for an agent to self-correct, or when the platform has no self-serve access at all.
What does RapidEye actually do?
RapidEye is AI inspection intelligence for property condition: we analyze the turnover photos and video walkthroughs operators already collect and flag damage, missing items, and staging issues. The gateway exists because the operators building their own tools are the same people who care about that. See the inspection API or the main site.
Start with a call, or just call the API
Fifteen minutes covers what you are building and turns the connector on for your account. Or point your agent at the API root first; every gated answer carries this same booking link.