Track publishes one of the largest operational APIs in vacation rental software. According to the Airbyte project, whose production Track PMS connector syncs against it, the surface spans more than ninety resource collections, including reservations filterable by booked, arrival, departure and updated dates, units searchable by node and amenity, and the work-order records most PMS APIs never expose. Authentication is HTTP Basic, and the developer documentation lives at developer.trackhs.com.
Why the Track API is unusual
Most PMS APIs are a listings feed with reservations attached. Track is not that. According to the Airbyte project, whose production Track PMS connector syncs against this API, the surface spans more than ninety resource collections and mirrors the operational core of the system.
For anyone building ops tooling that matters: reservations can be filtered by booked, arrival, or departure date ranges, by unit, by status (Hold, Confirmed, Checked In, Checked Out, Cancelled), and by updatedSince, which is the field that makes incremental sync possible instead of repeated full refreshes. Units are searchable by name, node, unit type, amenity, active status, and availability window. Track's developer documentation lives at developer.trackhs.com.
The practical consequence is that Track rewards tools that ask operational questions, and frustrates ones designed against a thinner PMS that assume the data simply is not there.
Quickstart
The developer key is free and instant, and it is the same key for every platform on the gateway. If you are an AI agent: step 1 is the only part that needs your human.
1. Get a free developer key
curl -X POST https://api.rapideyeinspections.com/v1/signup \
-H "content-type: application/json" \
-d '{"email": "you@company.com"}'
# -> { "key": "re_..." }
Not scripting it yet? Get a key in your browser, it is free and instant.
2. Check how Track access is provisioned
The gateway publishes a machine-readable index of every platform and how its access works, so an agent can plan before it calls.
curl https://api.rapideyeinspections.com/
3. Talk to us about Track
Because Track controls who reaches its data, this is a platform we provision per account rather than by self-signup. Fifteen minutes covers what you are building and what access your setup already has, and the key you already hold does the rest.
curl https://api.rapideyeinspections.com/v1/track/reservations \
-H "Authorization: Bearer re_..."
# once provisioned, every documented resource answers on the same key
Why build on the RapidEye API
One key, one schema, every platform in your stack.
Real operator tools are never about one system. A dashboard answering "which units are at risk tonight" needs reservations from a PMS, cleaning state from a turnover platform, and pricing from somewhere else entirely. Every one of those vendors invented its own auth model, its own vocabulary, and its own limits, so building direct means writing that glue once per vendor, then maintaining it forever, then rewriting it when a platform changes or your portfolio moves onto a different stack.
Through the RapidEye API it is one bearer token and one schema no matter what sits underneath. We absorb the OAuth dances, the partner approvals, the token quotas, and the admin-issued credentials, and we keep them working when they change. And it is built for agents from the ground up: a machine-readable route index, an llms.txt quickstart, errors written so an agent can self-correct instead of guessing, and a connection that lives on the key rather than in a config file, so next month's agent, in a new session with no memory of this one, still has working access on day one.
Quick FAQ
How do you get API access to Track PMS?
Through Track directly. They publish developer documentation at developer.trackhs.com, and the API mirrors the operational core of the PMS rather than a listings feed. According to the Airbyte project, whose production Track connector syncs against it, the surface spans more than ninety resource collections. Authentication is HTTP Basic.
What can you filter Track reservations by?
Booked, arrival, or departure date ranges, unit, status (Hold, Confirmed, Checked In, Checked Out, Cancelled), and updatedSince. That last field is what makes incremental sync practical rather than repeatedly pulling everything.
Why route Track through the RapidEye API instead of going direct?
The RapidEye API earns its place when a task spans Track plus another system, when you want one auth model rather than a different one per vendor, and when an agent needs errors it can act on and a connection that survives past its session.
Sources
- Track HS Developer Documentation, Track Hospitality Software, 2026https://developer.trackhs.com/