OwnerRez
OwnerRez is vacation-rental and short-term-rental property management software for hosts, owners, and property managers, covering channel management, bookings, guest CRM, quoting, payments, messaging, reviews, and a hosted booking website. The OwnerRez API v2 is a REST/JSON API served under https://api.ownerrez.com/v2 that exposes bookings, properties, listings, guests, inquiries, quotes, reviews, guest messaging, payments and financials, custom fields and tags, owners, and outbound webhook subscriptions. Requests are authenticated with an OAuth 2.0 access token (Authorization Code Grant) or with an API key / Personal Access Token via HTTP Basic auth, and server-to-app events are delivered through outbound webhooks.
Limited machine-readable signal and partial portal coverage — documentation a human can read, but little a machine or agent can consume without scraping.
API Evangelist profiles OwnerRez the way a machine reads it — 31 machine-readable artifacts across 23 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — OwnerRez scores 40.3/100 (thin), with a separate agent-readiness read of 48/100 (agent ready). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile OwnerRez
Each block below is one kind of artifact we hold for OwnerRez. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 23
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
OwnerRez Bookings API
Reservations against a property, including dates, guest, and charges.
OwnerRez Deposits API
Security and damage deposits.
OwnerRez Discounts API
Discount rules.
OwnerRez Fees API
Fees applied to bookings and quotes.
OwnerRez FieldDefinitions API
Definitions of custom fields.
OwnerRez Fields API
Custom field values attached to records.
OwnerRez Guests API
Guest contact records and their addresses, emails, and phones.
OwnerRez Inquiries API
Inbound guest inquiries and leads.
OwnerRez Listings API
Public listing content and channel listing sites for properties.
OwnerRez Messages API
Guest messaging threads and outbound messages.
OwnerRez Owners API
Property owners.
OwnerRez Payments API
Payments recorded against bookings.
OwnerRez Properties API
Rental properties managed in OwnerRez.
OwnerRez PropertySearch API
Availability and criteria search across properties.
OwnerRez Quotes API
Price quotes generated for a stay.
OwnerRez Refunds API
Refunds issued against payments.
OwnerRez Reviews API
Guest reviews collected for stays and properties.
OwnerRez SpotRates API
Ad hoc nightly spot-rate overrides.
OwnerRez Surcharges API
Surcharge rules applied to bookings and quotes.
OwnerRez TagDefinitions API
Definitions of tags.
OwnerRez Tags API
Tag values applied to records.
OwnerRez Users API
The authenticated user context.
OwnerRez WebhookSubscriptions API
Outbound webhook subscriptions and their event categories.
Scroll within the panel for all 23 ·
Open Collections 1
Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
OwnerRez API v2
OPEN COLLECTIONPricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the six things the Kin Score reads for commercial clarity.
Published pricing tiers and plan structures.
Rate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Ownerrez Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.
Cost, billing, and metering signals for API financial operations.
Ownerrez Finops
FINOPSSecurity Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Scopes 1
OAuth scopes are the vocabulary of least-privilege access. Profiling them shows exactly what an integration — or an agent acting on a user's behalf — is allowed to do.
OAuth scopes governing access to this provider's APIs.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for OwnerRez — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Documentation 1
Reference material describing how the API behaves
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 3
Authentication, authorization, and security posture
Operate 1
Status, limits, changes, and where to get help
Commercial 2
Pricing, plans, and the legal terms of use
Company 3
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/ownerrez · machine-readable index on apis.io