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

# Ownerreservations OwnerRez API

OwnerRez vacation rental management API. The API exposes 34 endpoints secured with basic authentication.

## For AI agents

Programmatically list properties, get propertie. Covers 34 operations with basic authentication.

## Scope

Does not handle payments, communications, or crm - use for e-commerce only.

## Capabilities

- List properties
- Get propertie
- Create booking

## Use cases

### E-Commerce Operations

Use the OwnerRez API to perform e commerce operations programmatically. The API provides 34 endpoints covering core functionality including list properties, get propertie, create booking.

Example prompt: Call GET /properties to list properties

### Automated Bookings Management

Automate bookings operations by combining multiple OwnerRez API endpoints. Agents can get propertie and then create booking in a single workflow.

Example prompt: Call GET `/properties/{id}` to get propertie, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call OwnerRez API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle basic tokens manually.

Example prompt: Search Jentic for 'list properties', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/properties` | List properties |
| GET | `/properties/{id}` | Get propertie |
| POST | `/bookings` | Create booking |
| GET | `/bookings` | List bookings |
| GET | `/bookings/{id}` | Get booking |
| POST | `/quotes` | Create quote |
| GET | `/quotes` | List quotes |
| GET | `/quotes/{id}` | Get quote |

## Key resources

- **Bookings** — Operations for bookings
- **Channels** — Operations for channels
- **Charges** — Operations for charges
- **Discounts** — Operations for discounts
- **Fees** — Operations for fees

## Why Jentic

- **Setup:** Wiring OwnerRez by hand means building and sending HTTP basic auth on every property, booking, and quote call. Through Jentic you install once, import the OwnerRez API from the API Directory, store the basic credentials once, and your agent calls it.
- **Permission scoping:** OwnerRez puts the resource id in the URL path (`/properties/{id}`, `/bookings/{id}`), so a rule can pin your agent to one property or booking for the reads it needs. You choose the operations it may call, so creating a booking or quote is not included unless you add it.
- **Credential handling:** Your OwnerRez basic credentials are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'list properties' or 'create a booking quote', and Jentic returns the matching OwnerRez operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Shopify** — Alternative e commerce API
- **Stripe** — Alternative e commerce API

## FAQ

### What authentication does the OwnerRez API use?

The OwnerRez API uses HTTP Basic authentication with username and password. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.

### Can I list properties with the OwnerRez API?

Yes. Use the GET /properties endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the OwnerRez API?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

### How do I list properties through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'list properties'. Jentic returns the matching OwnerRez API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the OwnerRez API have?

The OwnerRez API exposes 34 endpoints covering bookings, channels, charges operations.

### Can I limit what my agent is allowed to do with the OwnerRez API?

Yes. Jentic One is self-hosted by you, so your own rules decide which OwnerRez operations and credentials the agent may use. Because OwnerRez puts the resource id in the URL path, such as `/properties/{id}` and `/bookings/{id}`, you can pin the agent to a single property or booking for the reads it needs. You also choose the operations it may call, so writes like POST /bookings or POST /quotes stay off unless you explicitly add them.