Open API
Build on SERVOS with an open API
Sell from a website your developer builds
The Storefront API gives your site the catalog, live availability and the cart. Guests pay on the SERVOS checkout.
Storefront API
Your website shows rooms, trips, sauna sessions and events with live availability, sells passes, and fills the guest’s cart.
API keys
Admins create a key for each connection in settings, and rotate or revoke it at any time.
Build custom integrations on your bookings
The Admin API sends orders, line items and revenue to any system your developer connects. It only reads, and never sends a guest’s personal details.
Custom integrations
Your developer connects SERVOS to the systems you run, from a data warehouse to an in-house tool.
Admin API
Your own systems read orders, line items and revenue. Customers come without names, emails or phone numbers.
Incremental sync
Fetch only what changed since the last sync, check-ins and no-shows included.
MCP serverComing soon
Connect AI assistants to SERVOS through the Model Context Protocol.
Read the API docs before you sign up
Your developer can read the API docs today, without an account or a sales call.
Public API docs
The API docs are public, with a plain-text copy for AI assistants.
Works with
Land API bookings on the guest’s order
One plan for the whole hotel
3% platform fee with SERVPAY, plus standard card processing. The platform fee grows only as your sales do.
Everything included
- Rooms, guided trips, sauna sessions & tickets
- One calendar for rooms, trips and sauna
- One checkout for the stay, the trips and the sauna
- Guest profiles
- Keep Booking.com and Expedia in sync
- Auto-charge OTA virtual cards (VCC)
- Your own booking pages on your website
- Point of sale
- Card terminal sales at the counter
- Add-ons, upsells & discount codes
- Reporting & data export
- Data import from existing systems
In every plan
- Every product
- Unlimited users
- Unlimited bookings
PCI compliant
SERVPAY is PCI Level 1 compliant. SERVOS never sees full card numbers.
GDPR compliant
Guest data is protected and processed according to EU regulation.
Hosted in the EU
EU-based infrastructure with GDPR-conscious subprocessors.
Business types
Built for places that sell more than rooms
Destination hotels
Sell the trips and the sauna with the room.
Resorts
Rooms, trips and treatments on one guest bill.
Lodges & retreats
The bed, the guided days and the meals, sold as one stay.
Cabins & campsites
Cabins, pitches and extras, booked on your website and the booking sites.
Guided excursions
Departures with fixed seats, sold to guests and day visitors.
Event venues
Tickets, dinner and a room for the night in one order.
Saunas & bath houses
Shared sessions with a headcount, drop-ins and passes.
Spa hotels
Treatments, circuits and stays on one guest profile.
Questions you probably have
If yours isn’t here, ask us directly.
A documented way for other software to work with SERVOS. Your developer or agency uses it to connect your website and your own systems.
A booking flow on your own website or app with the Storefront API, and custom integrations that send orders and revenue to your own systems with the Admin API.
Yes. Your developer builds the integration on the Admin API, which sends bookings and revenue to any system.
No. Each customer comes as a fixed ID, without a name, email, phone number or address.
Owners and admins, under Settings → API keys. Each key can be rotated or revoked at any time.
Under Resources → Developers in the menu at the top of this page. Anyone can read them.
The API comes with the one SERVOS plan and every other product, at no extra fee. The plan is a monthly fee plus 3% of sales plus card processing.
Make room for more
Thirty minutes with us, and you’ll know whether SERVOS can run your next season.