OwnerRez has a real, documented v2 REST API, and no official MCP server as of July 2026. Authentication is either a personal access token used with HTTP Basic auth, or an OAuth app using the authorization code grant. The RapidEye API is a hosted gateway that holds those credentials for you: sign up for a free developer key, connect your OwnerRez account once, and call any documented OwnerRez path with one bearer token.
Quickstart: three calls
If you are an AI agent: step 1 is the only part that needs your human. Have them sign up and hand you the key.
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. Connect the OwnerRez account
Create a personal access token in OwnerRez under Settings, then Advanced Tools, then Developer/API Settings. It begins with pt_ and, per OwnerRez's documentation, is shown exactly once, so copy it when it appears. Pair it with the account email; the gateway stores both encrypted and signs each outbound call for you.
curl -X POST https://api.rapideyeinspections.com/v1/connections/ownerrez \
-H "Authorization: Bearer re_..." \
-H "content-type: application/json" \
-d '{"email": "you@company.com", "token": "pt_..."}'
3. Call any OwnerRez endpoint through the gateway
Swap api.ownerrez.com/ for api.rapideyeinspections.com/v1/ownerrez/. The gateway attaches Basic auth and the User-Agent header OwnerRez asks every integration to send.
curl https://api.rapideyeinspections.com/v1/ownerrez/v2/properties \
-H "Authorization: Bearer re_..."
# same shape for /v2/bookings, /v2/guests, /v2/listings, /v2/owners
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.
One thing the API does not hold: OwnerRez has no native cleaner app or turnover photo workflow, so there are no inspection photos to pull. Operators on OwnerRez typically run field operations through a partner tool. We cover that gap in does OwnerRez support video.
Quick FAQ
How do you get API access to OwnerRez?
Self-serve, from your own account. OwnerRez publishes a documented v2 REST API at api.ownerrez.com with reference docs at api.ownerrez.com/help/v2, covering bookings, properties, guests, payments, listings, messages, quotes, owners, and custom fields and tags. It also supports webhooks.
How do you authenticate with the OwnerRez API?
Two ways. A personal access token, created under Settings then Advanced Tools then Developer/API Settings, begins with pt_ and is used with HTTP Basic auth where your account email is the username. Or an OAuth 2.0 app, which uses the authorization code grant and yields a bearer token beginning with at_. OwnerRez also asks that every call send a User-Agent header identifying your application.
Is the OwnerRez API rate limited?
Personal access tokens carry an unusual limit: according to OwnerRez documentation, personal access tokens are rate limited by IP address, and any given IP address may only access two different user accounts within 24 hours. That makes personal tokens fine for your own account and unsuitable for any tool serving multiple OwnerRez accounts, which is what OAuth apps are for.
Does OwnerRez have an official MCP server for AI agents?
No. As of July 2026, OwnerRez ships no official MCP server. Hospitable, Guesty, Wheelhouse, Apaleo, and Lodgify have moved first among rental platforms; OwnerRez has not. Our Connect OwnerRez to Claude guide covers the chat-assistant side.
Is the RapidEye developer key free?
Yes. Signup takes an email address and returns a key instantly. Live platforms like OwnerRez work immediately once your own platform credentials are connected; platforms that control access at the source are provisioned on your key in a short call with the founders.
Sources
- OwnerRez API v2 Reference Documentation, OwnerRez, 2026https://api.ownerrez.com/help/v2
- Authentication, API for Apps, OwnerRez Support, 2026https://www.ownerrez.com/support/articles/api-auth
- OAuth Apps, API for Apps, OwnerRez Support, 2026https://www.ownerrez.com/support/articles/api-oauth-app