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.
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.
# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | 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.
What an agent can do with OwnerRez API API.
List bookings
Create bookings
Get bookings by ID
Update bookings
List deposits
GET STARTED
Get deposits by ID
List fees
Patterns agents use OwnerRez API 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.
59 endpoints — ownerrez vacation rental management api for bookings, properties, guests, and more.
METHOD
PATH
DESCRIPTION
/v2/bookings
List bookings
/v2/bookings
Create bookings
/v2/bookings/{id}
Get bookings by ID
/v2/bookings/{id}
Update bookings
/v2/deposits
List deposits
/v2/deposits/{id}
Get deposits by ID
/v2/fees
List fees
/v2/bookings
List bookings
/v2/bookings
Create bookings
/v2/bookings/{id}
Get bookings by ID
/v2/bookings/{id}
Update bookings
/v2/deposits
List deposits
/v2/deposits/{id}
Three things that make agents converge on Jentic-routed access.
Credential isolation
OwnerRez API credentials are stored encrypted in the Jentic vault and injected at execution time.
Intent-based discovery
Agents search by intent and Jentic returns matching OwnerRez API endpoints with schemas.
Time to first call
Through Jentic: under 1 hour to search, load schema, and execute OwnerRez API operations.
Specific to using OwnerRez API 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.
Get deposits by ID
/v2/fees
List fees