OwnerRez API
Official vendor OpenAPI document · agent-readyE CommerceOrder Managementbearer59 EndpointsREST
For Agents
OwnerRez vacation rental management API for bookings, properties, guests, and more.
Use for: I need to access OwnerRez API, How do I use the ownerrez.com API?, Get data from ownerrez.com
Not supported: Provides access to OwnerRez API functionality as defined in the OpenAPI specification.
OwnerRez vacation rental management API for bookings, properties, guests, and more.
Install Jentic One Beta
Connect the OwnerRez API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the OwnerRez API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fownerrez.com%2Fownerrez" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fownerrez.com%2Fownerrez" | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with OwnerRez API.
List bookings
Create bookings
Get bookings by ID
Update bookings
List deposits
Get deposits by ID
List fees
Use Cases
Patterns agents use OwnerRez API for, with concrete tasks.
★ Basic OwnerRez API Integration
Integrate OwnerRez API into your application to access its core functionality.
Use the OwnerRez API API to access vendor services and data.
Key Endpoints
59 endpoints — ownerrez vacation rental management api for bookings, properties, guests, and more.
METHOD
PATH
DESCRIPTION
GET
/v2/bookings
List bookings
POST
/v2/bookings
Create bookings
GET
/v2/bookings/{id}
Get bookings by ID
PATCH
/v2/bookings/{id}
Update bookings
GET
/v2/deposits
List deposits
GET
/v2/deposits/{id}
Get deposits by ID
Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring this OwnerRez API by hand means carrying its bearer token on every booking, deposit, and fee call and paging the collection endpoints yourself. Through Jentic you install once, import the OwnerRez API from the API Directory, store the token once, and your agent calls it.
Permission scoping
OwnerRez puts the resource id in the URL path (/v2/bookings/{id}), so a rule can pin your agent to one booking for reads and the specific edits you allow. You choose the operations it may call, so creating or patching bookings is not included unless you add it.
Credential isolation
Your OwnerRez bearer token is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'list bookings' or 'read a deposit', and Jentic returns the matching OwnerRez operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
FAQs
Specific to using OwnerRez API through Jentic.
What authentication does the OwnerRez API use?
The OwnerRez API uses bearer authentication.
How many endpoints does the OwnerRez API have?
The OwnerRez API has 59 endpoints available.
Can I limit what my agent is allowed to do with the OwnerRez API?
Yes. Because you run Jentic One yourself, your own rules decide which OwnerRez operations and credentials the agent may use. OwnerRez puts the resource id in the URL path, such as /v2/bookings/{id}, so you can pin the agent to reading a single booking, deposit, or fee and to only the specific edits you approve. Since you pick the operations it can call, actions like creating a booking with POST /v2/bookings or patching one with PATCH /v2/bookings/{id} stay off limits unless you add them.
GET STARTED