Skip to main content
Unifystays is a single, unified API for all your hotel suppliers. Your application integrates with one consistent API while Unifystays handles supplier connections, static hotel content, mappings, and normalized responses behind the scenes. Once your Unifystays integration is live, adding another supported supplier is a portal configuration change, not a new integration project.
Enabling another supplier does not require new supplier API code, static inventory tables, synchronization jobs, or mapping logic in your system.

Why Unifystays

A direct supplier integration usually requires much more than connecting to a booking endpoint. For every supplier, your team must:
  • Import and store the supplier’s static hotel inventory in your own database.
  • Build scheduled jobs to keep hotel content and mappings up to date.
  • Map supplier-specific hotel, room, rate, meal plan, and destination data to your own model.
  • Build and maintain separate search, availability, prebook, booking, and cancellation integrations.
  • Update your system whenever a supplier changes its API or data format.
The same work starts again when you add another supplier, often turning supplier onboarding into a project that takes weeks or months. Unifystays replaces those separate integrations with one stable contract:

How It Works

1

Sign in to the portal

Go to unifystays.com and sign in to your Unifystays account.
2

Choose an environment

Use Sandbox while building and testing. Switch to Production when you are ready for live traffic.
3

Configure your suppliers

Select a supported supplier, enter the credentials issued by that supplier, and enable it for the selected environment.
4

Create an API key

Create and manage your own API key in the portal for the selected environment. You do not need to request a key from support.
5

Integrate once

Connect your backend to the Unifystays API using the environment’s base URL and send the API key in the x-api-key header.
6

Enable more suppliers

Add another supported supplier from the portal whenever you need it. Your API endpoints and integration flow remain the same.

Environments

Unifystays provides separate environments for testing and live bookings.
Create and use the API key for the same environment as the base URL. Keep sandbox and production keys separate, and never expose either key in browser or mobile application code.

What Your Integration Covers

The unified API provides a consistent workflow across your enabled suppliers:
  • Destination and hotel discovery.
  • Normalized hotel content without supplier-specific static inventory storage.
  • Hotel search and live supplier pricing.
  • Room availability and bookable room options.
  • Prebooking to verify availability and price.
  • Idempotent booking to protect against duplicate reservations.
  • Booking retrieval, status tracking, and cancellation.

Booking Flow

1

Resolve the destination

Use Destination Autocomplete to get a city, hotel, or place identifier.
2

Search hotels

Use Search Hotels with the destination, stay dates, rooms, and guest nationality.
3

Fetch rooms

Use Get Room Options to get live room options and a booking_token.
4

Prebook

Use Prebook a Room with the booking_token to confirm price and availability.
5

Book

Use Create Booking with an Idempotency-Key and the unifystays_prebooking_id.
6

Track or cancel the booking

Retrieve the booking until it reaches its final state, or send a cancellation request when required.

Response Shape

Most successful responses follow this envelope:
Every response includes an X-Request-Id header. Include that value when contacting support. Make your first sandbox request