Track PMS
Business software
Sync Track PMS reservation, unit, guest, and folio data into your warehouse. Ingest builds this connector the first time a customer asks for it, then keeps the tables current in a data warehouse you own, on the schedule you choose.
The Track PMS connector syncs your vacation rental and hospitality property management data into analytics-ready tables in your data warehouse. Pull reservations, units, guests, and folios from the Track PMS API, with Ingest handling auth, pagination, and retries so the tables stay current.
What you would get
Each of these arrives as its own table, kept current on the schedule you choose:
- Reservations
- Units
- Guests
- Folios
How it gets built
- Choose Track PMS when you set up a pipeline, with the warehouse it goes to and a schedule.
- Ingest reads Track PMS's documentation, and you choose the tables you want.
- Ingest builds the connector and tests it against Track PMS itself.
- A person at Ingest reviews and publishes it, and your pipeline starts on its own.
What you will need
Basic Auth or HMAC (Acquia HTTP HMAC spec). Not self-serve: credentials are generated by TrackHS per tenant, and API testing is only provided for customers under contract.
You enter it once, in a form in Ingest, and it is kept in a secret store set aside for your organization.
Questions
- Does Ingest have a Track PMS connector?
- Not as a finished connector yet. Ingest builds it from Track PMS's own documentation the first time a customer asks, tests it against the real service, and lists it once it passes.
- Which warehouses can Track PMS data go to?
- Amazon S3, Google Cloud Storage, Azure Blob Storage, Apache Iceberg, Ingest Managed Lakehouse, MotherDuck, Postgres, Amazon Athena, Databricks, Redshift, BigQuery, ClickHouse, MySQL / generic SQL and Snowflake, in an account you own.
- Do I need to write code?
- No. Ingest builds, runs and maintains the connector. Someone with access to your warehouse connects it once, following a short guide.
Track PMS API documentation: https://developer.trackhs.com/docs/authentication
Where this would land, and what else connects
Setting up the destination is its own short guide, one per warehouse or lake: Amazon S3, Google Cloud Storage, Azure Blob Storage, Apache Iceberg, Ingest Managed Lakehouse, MotherDuck, Postgres, Amazon Athena, Databricks, Redshift, BigQuery, ClickHouse, MySQL / generic SQL, Snowflake.
Other sources Ingest connects for SaaS teams: Asana, Jira, Airtable, Clockify, Facebook Ads, Frankfurter.