canonical: https://jentic.com/apis/ownerrez.com/ownerrez

# OwnerRez API

OwnerRez vacation rental management API for bookings, properties, guests, and more.

## For AI agents

OwnerRez vacation rental management API for bookings, properties, guests, and more.

## Scope

Provides access to OwnerRez API functionality as defined in the OpenAPI specification.

## Capabilities

- List bookings
- Create bookings
- Get bookings by ID
- Update bookings
- List deposits
- Get deposits by ID
- List fees

## Use cases

### Basic OwnerRez API Integration

Integrate OwnerRez API into your application to access its core functionality.

Example prompt: Use the OwnerRez API API to access vendor services and data.

## Key endpoints

| 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 |
| GET | `/v2/fees` | List fees |

## Key resources

- **Main API** — Primary OwnerRez API resources and operations

## Why Jentic

- **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 handling:** 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.
- **Discovery method:** 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.

## FAQ

### 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.