Reference · built on requestConnectorHospitality & property systems

OwnerRez

Bookings, guests, properties, quotes, and guest messages from OwnerRez vacation rental accounts.

Request accessPricing ↗

About

OwnerRez is vacation rental management software for owners and property managers. Its REST API v2 at api.ownerrez.com covers bookings, guests, properties, listings, quotes, inquiries, messages, payments, deposits, refunds, reviews, and calendar nights, with webhook subscriptions that push each change as it happens.

Through Fibric, an operator watches bookings and guest threads as they change, then proposes a reply, a tag, or a quote for your approval. Each change is applied once and leaves a receipt: what changed, why, and how to undo it.

This is a reference listing. It documents what Fibric would read from OwnerRez and what it could propose, based on the vendor's published interfaces. Fibric builds it under a managed deployment when you request it; selecting it here installs nothing.

Inputs

  • Bookings through GET /v2/bookings, filtered by property_ids or since_utc, with status Active, Pending, or Canceled
  • Booking changes by webhook category: agreement, availability, canceled, charge, dates, doorcode, financial, notes, payment, property, time, transaction
  • Guests, inquiries, and quotes, with guest webhooks on the info category
  • Properties, listings, listing sites, and calendar nights per property through GET /v2/calendar/{property_id}
  • Payments, deposits, refunds, fees, and surcharges as read-only records
  • Guest message threads through GET /v2/messages with threadId and since_utc, plus thread_message webhooks
  • Guest reviews through GET /v2/reviews

Proposed actions

  • Target capability: propose a reply on a guest thread through POST /v2/messages
  • Target capability: propose a tag on a booking or guest through POST /v2/tags
  • Target capability: propose a quote through POST /v2/quotes, or a change to one through PATCH /v2/quotes/{id}
  • Target capability: propose a field value on a booking through POST /v2/fields
  • Target capability: propose a booking change through PATCH /v2/bookings/{id}

Proposed actions are target capabilities. Every action runs propose-first and needs a validated deployment and the appropriate permissions.

What you can build

  • Prepare each arrival

    Booking webhooks on the dates, doorcode, and agreement categories show what is still missing before check-in. The operator proposes the guest message or tag that closes the gap.

    With Arrival Prep, Pre-Arrival Fix

  • Answer guest threads in time

    New thread_message webhooks land with the full message. The operator drafts a reply on the thread through POST /v2/messages and holds it for your approval.

    With Guest Requests

  • Reply to reviews

    Reviews arrive through GET /v2/reviews. The operator drafts a response for each and records which booking it belongs to.

    With Review Reply

  • Recover after a bad stay

    A canceled or financial booking change, or a low review, opens a recovery case. The operator proposes the next step and leaves a record.

    With Service Recovery

Requirements

  • An OwnerRez account with Developer/API Settings access to create a Personal Access Token or an OAuth app
  • For webhooks, an OAuth app: OwnerRez sends webhooks only to OAuth-authenticated apps, at an https:// URL with basic auth
  • A User-Agent header on every OAuth request carrying the app name and client id
  • Content-Type and Accept set to application/json; the API speaks JSON only
Authentication
An OAuth 2.0 app (authorization code grant at https://app.ownerrez.com/oauth/authorize, bearer tokens starting at_, thirty-day expiry) or, for one account, HTTP Basic with your email and a pt_ Personal Access Token.

Limits

  • A per-IP rate limit of 300 requests every 5 minutes; excess requests return 429
  • Personal Access Tokens may reach only two user accounts per IP address in 24 hours
  • Webhooks wait 4 seconds for a 2xx, retry up to 10 times, then stop; duplicates are possible and carry the same payload id
  • Booking lists require property_ids or since_utc; list pages return at most 100 records

Access and pricing

Reference listing. Fibric builds the connector under a managed deployment when you request it. Your quote covers the build, capabilities, usage, and support.

Request OwnerRez ↗

Questions and answers

Does OwnerRez send webhooks?
Yes, for OAuth apps. Set a webhook URL, user, and password on the app. OwnerRez posts entity_create, entity_update, and entity_delete events for booking, guest, inquiry, property, quote, and thread_message, with the full entity in the payload. Failed deliveries retry up to 10 times.
Can I use a Personal Access Token instead of OAuth?
For your own account, yes: Basic auth with your email and a pt_ token. OwnerRez limits tokens by IP to two user accounts per 24 hours and does not send webhooks to token-based access, so a deployment across accounts needs an OAuth app.
What is the rate limit?
300 requests per IP every 5 minutes. Over the limit, every request returns HTTP 429 with a JSON body of code 429 and error Rate limit exceeded until usage falls below the limit. OwnerRez recommends queuing webhooks and keeping a local map of entity ids.
Ask about OwnerRez

Ask about the capabilities and requirements in this listing.

For project-specific requirements, contact Fibric.

This connector listing is developed, published, and supported by Fibric. It describes integration with OwnerRez through published interfaces. Third-party names and logos identify the systems an integration connects to; they are the property of their respective owners, who are not affiliated with Fibric and do not sponsor or endorse this listing. Trademark policy