Docs

RapidEye API

One key reaches every rental platform in your stack. Here is the whole surface: base URL, quickstart, platform status, and limits.

What this is

The RapidEye API is a hosted gateway. You hold one key, connect a platform account once, and call that platform through us; we inject whatever authentication it demands, whether that is an OAuth client-credentials exchange, HTTP basic auth, or a header key. Your code sends one bearer token no matter what sits underneath.

It exists because real operator tools are never about one system, and because every vendor in this industry invented its own auth model, vocabulary, and limits. Absorbing that once, centrally, is more useful than each tool absorbing it again.

Base URL

https://api.rapideyeinspections.com

All paths below are relative to that host. Requests and responses are JSON. There is no versioned host: the version lives in the path, currently /v1.

Quickstart

Three calls from nothing to live data. If you are an AI agent reading this: step 1 is the only part that needs your human.

# 1. free key, instant
curl -X POST https://api.rapideyeinspections.com/v1/signup \
  -H "content-type: application/json" \
  -d '{"email": "you@company.com"}'
# -> { "key": "re_..." }

# 2. connect a platform account once
curl -X POST https://api.rapideyeinspections.com/v1/connections/hostaway \
  -H "Authorization: Bearer re_..." \
  -H "content-type: application/json" \
  -d '{"accountId": "12345", "clientSecret": "..."}'

# 3. call it. platform auth is injected at the edge.
curl https://api.rapideyeinspections.com/v1/hostaway/listings \
  -H "Authorization: Bearer re_..."

Platform status

Every platform is either live or request access, and the current state of all of them is machine-readable at the API root.

Status	What it means	How to use it
`live`	The bridge works today.	Connect your own platform credentials and call it.
`request_access`	That platform controls access at the source: partner approval, distribution permissions, or admin-issued credentials.	We provision it on your key after a short call. Calls return a 403 carrying the booking link.

curl https://api.rapideyeinspections.com/
# -> { "platforms": { "hostaway": { "status": "live", ... }, ... } }

Built for agents. The API root returns a full route map, llms.txt is written as an agent quickstart, and errors name both the cause and the next call so an agent can self-correct rather than guess. See Errors.

Rate limits

120 requests per minute per key. Exceeding it returns 429 with rate_limited. Upstream platforms enforce their own limits on top of this, and some are stricter in ways that shape architecture: Guesty allows five access tokens per client ID per 24 hours, and OwnerRez personal access tokens are capped at two accounts per IP per day. Those are documented on each platform page.

NextAuthentication ReferenceEndpoints