Docs/Knowledge Base/PMS Guides

OwnerRez API

OwnerRez exposes a REST API (v2) at api.ownerrez.com covering properties, bookings, quotes, guests, calendar, messages and webhooks, authenticated with HTTP Basic (account email plus a personal access token) for your own account, or OAuth 2.0 apps for other hosts’ accounts.

Written from running this integration in production. Last checked against the OwnerRez API on 11 November 2026.

OwnerRez API report card

From OwnerRez's own documentation. Checked on 11 November 2026.

Base URL / API style
https://api.ownerrez.com/v2. REST, JSON over HTTPS. Lists page with a cursor in next_page_url. source
Auth
HTTP Basic (account email + personal access token pt_…) for your own account, or OAuth 2.0 bearer tokens (at_…) through an OAuth app. Standard-policy tokens expire after 30 days and come with a refresh token. source
Rate limits
300 requests / 5 min per IP and 1,000 / 5 min per access token; a 429 carries Retry-After. A personal access token may reach only two different OwnerRez accounts from one IP address per 24 hours. source
Webhooks
OAuth apps only. One URL per app (with basic auth) or per-connection subscriptions; the payload carries the whole entity. Retries end after 10 attempts over about 4 hours, and webhooks pause app-wide when half or more of 100+ deliveries in about an hour fail. source
Read / write coverage
Read and write properties, bookings (guest, owner, block), quotes, guests and discounts; read the calendar, rates, reviews and listings. No operation cancels a booking. Reviews and listings need the Integrated Websites premium or an OAuth app with listing access. source
Guest messaging
OAuth apps only (a personal token gets a 402). Thread-scoped reads (GET /v2/messages?threadId=) and new messages; no endpoint lists all threads. Channel (Airbnb, Vrbo, Booking.com) and SMS threads; email threads are not available yet. source
Sandbox / test account
A stage environment at appstage.ownerrez.com with test card numbers; an SMS test number on request. source
Partner / marketplace programme
OAuth apps for software serving other hosts: contact partnerhelp@ownerrez.com, then create the app under Developer/API Settings. source
Restrictions worth knowing
Personal tokens are for your own account: token-based authentication “is intended for private usage, and is not designed for partner use or wide deployment.” source

What the OwnerRez API is

OwnerRez’s API v2 is a JSON REST API at https://api.ownerrez.com/v2. It covers properties, bookings (guest stays, owner stays and blocks), quotes, guests, the calendar, rates, discounts, reviews, listings, messages and webhook subscriptions. You can create a booking priced by the property’s own rules, hold dates with a quote and send the guest its payment link, and change a booking’s dates, guest counts and notes.

There are two ways in, and they are not interchangeable. A personal access token reads and writes your own account. An OAuth app is how software reaches other hosts’ accounts, and several parts of the API are open only to OAuth apps: webhooks, guest messaging, and reviews and listings for hosts without the Integrated Websites premium. OwnerRez says token-based authentication “is intended for private usage, and is not designed for partner use or wide deployment.”

Getting a token is self-serve and takes a minute. Which of the two credentials you build on decides most of what follows, so that choice comes first on this page.

How to get OwnerRez API access

  1. 1.For your own account: in OwnerRez, open Settings → Advanced Tools → Developer/API Settings and create a personal access token. It starts with pt_ and is shown once. A Team Access staff member with read-only access cannot create one.
  2. 2.Call the API with HTTP Basic auth against https://api.ownerrez.com/v2: your OwnerRez account email as the username and the token as the password.
  3. 3.For other hosts’ accounts: email partnerhelp@ownerrez.com about what you are building, then create an OAuth app in Developer/API Settings with a redirect URL, a webhook URL with a basic-auth user and password, and a scope of Full or Read. You get a client id (c_…) and a client secret (s_…, shown once).
  4. 4.Send each host to https://app.ownerrez.com/oauth/authorize, exchange the returned code (valid for 10 minutes) at https://api.ownerrez.com/oauth/access_token, and call the API with the at_… bearer token plus a User-Agent naming your app and client id. Under the recommended Standard policy, access tokens expire after 30 days and come with a refresh token.

Pick the OAuth scope carefully. An app created with Read can only make GET requests, and OwnerRez says you will not be able to create read-and-write tokens for it later.

What will bite you

From running this integration in production and reading the vendor's documentation line by line.

A personal token reaches two accounts per IP per day

OwnerRez’s rate-limiting guide: “a personal access token may only reach two different OwnerRez accounts from one IP address per 24 hours. An integration serving many customer accounts needs an OAuth app.” Build a multi-client tool on personal tokens and the third client’s calls from your server fail for a day. Test with two accounts and you will never see it. If you serve more than one host, build on OAuth from the start.

Messaging and webhooks are OAuth-only

Webhooks “are only available for OAuth-authenticated apps”, and messaging endpoints answer a personal access token with a 402. Messaging is also forward-only: no endpoint lists every thread or every message. GET /v2/messages returns one thread and needs ?threadId=; without it you get a 400. You learn about threads from message webhooks or from a booking, then read that thread.

Offset paging and unknown parameters stop working on January 5, 2027

Lists page with next_page_url, which carries an opaque cursor. From January 5, 2027, offset above 0 returns a 400, and so does any query parameter the reference does not list. Today an unknown one is silently ignored: send property_id instead of property_ids and a first load fails with “Either 'property_ids' or 'since_utc' is required”. Follow next_page_url exactly as returned, and start from page one when a filter changes.

A booking cannot be cancelled through the API

The booking edit model has no status field and v2 has no cancel or delete operation on bookings, so a cancellation has to be made in OwnerRez. Bookings created with generate_charges: true are priced from the property’s own rates, there is no field for a custom total, and changing dates or guest counts later does not recalculate the charges.

Webhooks: retries end, order is not guaranteed, and a pause loses events

Each delivery carries an id, and a retry reuses it, so drop ids you have processed. Retries stop after 10 attempts over about 4 hours. Order is not guaranteed, your own API writes come back as webhooks, and you can receive a delete for a record you never saw. Answer within 4 seconds: when 100 or more deliveries in about an hour fail at a rate of half or more, OwnerRez pauses webhooks for your whole app, and nothing from the paused period is sent later. Subscribing both in the app settings and per connection delivers every event twice.

Rate limits count per IP and per token, and a 429 costs five minutes

The limits are 300 requests per IP address and 1,000 per access token, each over any 5-minute window. A 429 carries Retry-After, which OwnerRez currently sets to 300 seconds. A bulk sync that ignores the limit does not slow down; it stops.

What it costs to keep working

Reading your own bookings with a personal token takes minutes. Serving other hosts is an OAuth integration with dates attached to it.

  • •January 5, 2027: offset paging above 0 and unrecognised query parameters start returning 400. Code that has worked for years breaks on that day.
  • •OAuth tokens on the Standard policy expire after 30 days, and OwnerRez is phasing out permanent tokens. Refresh tokens have to be stored and rotated for every host.
  • •Webhook handling: deduplicate by delivery id, tolerate events out of order, answer within 4 seconds, and plan for the app-wide pause. Nothing is replayed after it, so you need a catch-up read with since_utc.
  • •Premium gates: reviews and listings need the host’s Integrated Websites premium unless your OAuth app has listing access, and a gated call answers 402.

The same job, both ways

OwnerRez directly

# Your own account: HTTP Basic with your OwnerRez email and a personal token.
curl -s -u 'you@example.com:pt_YOUR_TOKEN' \
  'https://api.ownerrez.com/v2/bookings?property_ids=123&limit=100'

# Then request next_page_url, exactly as returned, until it is absent.
# A third host account from the same server IP within 24 hours needs an
# OAuth app instead, and so do messages and webhooks.

Through Repull

# Connect once with the same email and token.
curl -s -X POST 'https://api.repull.dev/v1/connect/ownerrez/credentials' \
  -H 'Authorization: Bearer sk_live_YOUR_KEY' \
  -H 'Content-Type: application/json' \
  -d '{"credentials": {"username": "you@example.com", "apiToken": "pt_YOUR_TOKEN"}}'

# Reservations from OwnerRez and every other connected PMS and channel,
# in one shape. `platform` says where each one came from.
curl -s 'https://api.repull.dev/v1/reservations?limit=100' \
  -H 'Authorization: Bearer sk_live_YOUR_KEY'

Why use Repull for OwnerRez

Your second client will not be on OwnerRez

If you only ever read your own OwnerRez account, call the v2 API directly with a personal token: it is all you need, and Repull would be a layer you do not need. The cost arrives with other systems, and with clients who have none.

One reservation shape across every system

An OwnerRez booking, a Guesty reservation and a Smoobu one come back from GET /v1/reservations with the same fields. platform says which channel each came from, so you do not keep a table of channel names per PMS.

Refused writes are refused before anything is sent

Where OwnerRez’s API cannot do something, such as cancelling a booking or setting a custom total, Repull answers 422 pms_write_unsupported naming OwnerRez, and capabilities.pms on the connection tells you in advance.

Every system has its own credential

OwnerRez is a personal token or an OAuth app with 30-day tokens. Smoobu signs every request with a key and secret. Beds24 swaps a single-use invite code for refresh tokens. Guesty allows five tokens a day. You keep one Repull key.

Channels next to the PMS

Some clients have no PMS at all. The same Repull key connects Airbnb, Booking.com and Vrbo directly, and more, alongside OwnerRez accounts.

Connect OwnerRez through Repull

Create a key, connect a OwnerRez account with the credentials OwnerRez issues, and read reservations in the same shape as every other system you support.

Frequently asked questions

Does OwnerRez have an API?

Yes. OwnerRez API v2 is a REST API at https://api.ownerrez.com/v2 covering properties, bookings, quotes, guests, calendar, rates, reviews, listings, messages and webhooks. Use a personal access token for your own account, or an OAuth app to reach other hosts’ accounts.

How do I get an OwnerRez API key?

In OwnerRez, open Settings → Advanced Tools → Developer/API Settings and create a personal access token. It starts with pt_ and is shown once. Call the API with HTTP Basic auth: your OwnerRez account email as the username and the token as the password.

What are the OwnerRez API rate limits?

300 requests every 5 minutes per IP address and 1,000 every 5 minutes per access token; a 429 carries Retry-After. Separately, a personal access token may only reach two different OwnerRez accounts from one IP address per 24 hours. An integration serving many accounts needs an OAuth app.

Why does my OwnerRez personal token fail for a third account?

Because a personal access token may only reach two different OwnerRez accounts from one IP address per 24 hours. Personal tokens are meant for your own account; OwnerRez asks integrations that serve other hosts to use an OAuth app.

Can I send guest messages through the OwnerRez API?

Only from an OAuth app: messaging endpoints answer a personal access token with a 402. Messaging is thread-based and forward-only. GET /v2/messages needs a threadId, and there is no endpoint that lists every thread, so you start from message webhooks or from a booking.

Does OwnerRez have webhooks?

Yes, for OAuth apps only. Set one URL with a basic-auth user and password in the app, or subscribe per connection with POST /v2/webhooksubscriptions. Retries stop after 10 attempts over about 4 hours, and OwnerRez pauses an app’s webhooks when too many deliveries fail.

Can I use OwnerRez and Repull together?

Yes. Repull connects with your OwnerRez email and a personal access token, the same credential you would use yourself, and changes nothing inside OwnerRez. Guest messages stay in OwnerRez, because its messaging API is open only to OAuth apps. To test first, OwnerRez runs a stage environment at appstage.ownerrez.com with test card numbers.

The other systems Repull connects

Reference

Auth Type

Personal access token (HTTP Basic) or OAuth 2.0

Required Fields

usernameapiToken

Supported Operations

✓ listings
✓ reservations
✓ calendar
— messages
— webhooks
— guests

Connection Guide

In OwnerRez, open Settings → Advanced Tools → Developer/API Settings and create a personal access token (it starts with pt_ and is shown once). Send your OwnerRez account email as username and the token as apiToken.

Notes

  • • HTTP Basic (account email + personal access token) or an OAuth 2.0 bearer token
  • • A personal access token reaches at most two OwnerRez accounts from one IP address per 24 hours
  • • Webhooks and guest messaging are available to OwnerRez OAuth apps only. Repull connects with a personal access token, so OwnerRez guest messages do not come through Repull: read and answer them in OwnerRez or on the booking channel
  • • OwnerRez’s API cannot cancel a booking: cancel it in OwnerRez
AI