In the Hostfully Platform API, a lead is a booking or inquiry record, not a sales prospect. Listing leads is how you read who is arriving, when, and at which property, while a separate orders endpoint carries the financial side of each booking. Hostfully ships no official MCP server as of July 2026, and API keys are self-serve from account settings, so the real barrier is vocabulary rather than access.
Leads, orders, and why the naming matters
Every platform models the same reality with different words, and Hostfully's choice catches people out. A lead in the Hostfully Platform API is the reservation itself: a booking or inquiry record. If you are looking for the endpoint that answers "who is arriving Friday," it is leads, not anything named reservations or bookings.
The financial side lives separately: orders hold the money attached to each booking. So a revenue question and an arrivals question hit two different endpoints that must be joined on your side.
This is exactly the class of detail that costs an agent an afternoon of guessing, and exactly what a normalized schema removes: through the gateway the same concept has the same name whether the platform underneath calls it a lead, a reservation, or a booking.
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_..." }
2. Check how Hostfully 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 Hostfully
Because Hostfully 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/hostfully/leads \
-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.
Sources
- Hostfully Platform API Documentation, Hostfullyhttps://docs.hostfully.com/