Linking OwnerRez as a source
Let AI connect your sources for you
Skip the manual setup — run this in your project and the wizard auto-detects your databases and APIs and connects them to PostHog.
This source is currently in alpha. The interface and available tables may change.
The OwnerRez connector syncs bookings, payments, guests, and more into the PostHog data warehouse, so you can analyze them alongside your product data.
Prerequisites
Credentials that can read the data you want to sync. PostHog only reads data, so read access is enough.
Adding a data source
- In PostHog, go to the Sources tab of the data pipeline section.
- Click + New source and click Link next to this source.
- Enter your credentials (see Configuration below) and click Next.
- Select the tables you want to sync, choose a sync method and frequency, then click Import.
Once the syncs are complete, you can start querying this data in PostHog.
Enter your OwnerRez account email and personal access token to pull your bookings, guests, payments, and property data.
Create a personal access token under Settings → Advanced Tools → Developer/API Settings in your OwnerRez account. OwnerRez rate limits personal access tokens per IP address to two accounts every 24 hours, so this connection method suits a single OwnerRez account rather than many.
You'll be asked for:
- Account email: for example
you@example.com. - Personal access token: for example
pt_....
Sync modes
Each table can be synced in one of several modes, depending on what the source supports:
- Webhook (when available) – the source pushes changes to PostHog in real time. Fastest freshness, lowest ongoing cost, and the only mode that reliably captures updates and deletes.
- Incremental – only new or updated rows are synced on each run, using a cursor field (such as an
updated_attimestamp). Cheaper than a full refresh, but deletes aren't captured. - Append only – new rows are appended using a cursor field; existing rows are never updated. Ideal for immutable, append-only tables like event logs.
- Full refresh – the whole table is reloaded on every sync. Use it when a table has no reliable cursor or when you need deletions reflected.
See sync methods for a full explanation of how each mode works and how to choose between them.
All OwnerRez tables are full refresh. Each sync replaces the contents of the table.
Configuration
| Option | Type | Required |
|---|---|---|
Account email | Yes | |
Personal access token | password | Yes |
Supported tables
| Table | Description | Sync method | Incremental field | Primary key |
|---|---|---|---|---|
Bookings | A guest reservation or blocked-off period against one of the account's properties. | Incremental, Full refresh | updated_utc | — |
Payments | A payment collected from a guest against a booking. | Full refresh | — | — |
Guests | A guest record — the person a booking or quote is made for. | Full refresh | — | — |
Properties | A rental property (listing) managed in the account. | Full refresh | — | — |
Quotes | A price quote generated for a prospective booking, before it's confirmed. | Incremental, Full refresh | updated_utc | — |
Deposits | A batch deposit of payments, refunds, and fees into the host's bank account. | Full refresh | — | — |
Fees | A fee charged on a booking (e.g. a cleaning fee or processing fee). | Full refresh | — | — |
Refunds | A refund issued to a guest against a booking. | Full refresh | — | — |
Reviews | A guest or host review left for a stay. | Incremental, Full refresh | updated_utc | — |
Troubleshooting
- If the connection fails with an authorization error, the personal access token is wrong, expired, or has been revoked. Create a new one, then reconnect the source.
- If a table syncs no rows, the credential may not have access to that data. Check its permissions, then reconnect the source.
If your sync is failing or data looks wrong, see the Data warehouse troubleshooting guide. If that doesn't help, contact support – we're happy to help.