Scheduling & Booking · Integration
HotelKey
Add HotelKey to your product for your customers, and give your AI agents governed access to it.
Embed a HotelKey integration so hospitality customers can bring their own property data into your product without exporting reports. Every property configures its own room types, rates, and required fields, so mapping is configuration per customer rather than code. fastn handles per-property authentication, pagination, and API upkeep, and large reads are throttled so a backfill does not exhaust a property's allowance.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let customers read their own reservations and guest records into your product, mapped to their fields.
Read room and rate configuration at runtime so your product reflects how each property is set up.
Write updates back so your product does not become a second source of truth for a booking.
Backfill historical reservations on a throttled import so a new property sees its data on day one.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent reads current reservations before answering a question about occupancy.
An agent updates a reservation record within governed permissions, with each action logged.
An agent reacts to a change on a booking and runs the next step of a workflow.
Example prompt
List tomorrow's arrivals with the room type booked and flag any reservation missing guest contact details.
Set up HotelKey in 4 steps
- 01Open the HotelKey connector from your fastn dashboard.
- 02Have each customer authenticate their own HotelKey account.
- 03Map the properties, records, and fields your product uses, then enable actions and triggers.
- 04Call them from your product, or expose them to an agent through the MCP server.
Why teams use the HotelKey integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a HotelKey integration without building it. Your customers connect their own HotelKey account inside your product and work their bookings, events and availability there, with no per-customer code on your side.
- Handle the part that actually costs time: availability is only true at the moment you read it, so a stale free/busy picture becomes a double booking somebody has to apologise for. fastn owns the auth, token refresh, rate limits, pagination and breaking-change fixes, so a HotelKey update is not your on-call problem.
- One integration serves your product and your agents. The same governed HotelKey connection powers in-product features and gives AI agents scoped, audited access, so you let people book and reschedule without leaving your product without wiring it twice.
Used by these teams
Works well with
Often used alongside
Tools the same teams tend to run next to HotelKey, across other categories.
HotelKey integration FAQ
How do I add a HotelKey integration to my product?
Enable the HotelKey connector in your fastn dashboard, then let each customer authenticate their own HotelKey account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no HotelKey client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own HotelKey account?
Yes. Every connection is scoped to the individual customer, so each authorises their own HotelKey account and only ever sees their own bookings, events and availability. That per-tenant isolation is the point of an embedded integration: you support the long tail of customer setups without maintaining an integration per customer.
Can AI agents use this HotelKey integration?
Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. An agent reads current reservations before answering a question about occupancy.
Who maintains the HotelKey integration?
fastn does. When HotelKey changes an endpoint, deprecates a field or alters its auth, the fix lands in the connector rather than in your backlog, and your customers' connections keep working.
Can my product create, reschedule or cancel bookings in HotelKey automatically?
Yes, in each customer's own account. Your product reads live availability, places a booking, moves it or cancels it, and reacts when someone books or cancels on the other side.
Does it respect each team's own availability rules in HotelKey?
Yes. Working hours, buffers, lead times, resource capacity and routing rules are configured per customer and mapped rather than hard-coded, so an unusual setup works without code from you.
What can I build with the HotelKey integration?
A common starting point: read their own reservations and guest records into your product, mapped to their fields. Teams also use it for the other use cases listed above, and expose it to agents for governed reads and writes.
How much does the HotelKey integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding HotelKey does not change your per-connector cost. You can start free with 3 connected accounts.
Add HotelKey to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.