Skip to main content
Unifystays gives your team control of supplier activation and API keys from the Unifystays portal. Your application integrates with one API once; supplier setup happens in the portal for each environment.

​
Configure an Environment

1

Sign in to the portal

Sign in to your Unifystays organization at unifystays.com.
2

Choose Sandbox or Production

Configure and test suppliers in Sandbox first. Use Production only for live search, booking, and cancellation traffic.
3

Enable a supplier

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

Create an API key

Create an API key for the same environment. You can manage and rotate keys in the portal without waiting for support.
5

Connect your backend

Send the API key in x-api-key with the matching base URL.

​
Base URLs

The current Sandbox/staging dataset includes only a limited number of places and hotels. This is intentional. Validate requests with destinations returned by Sandbox Destination Autocomplete; do not assume a place or hotel available in production is also seeded in Sandbox.
Sandbox and production keys are separate. A key must only be used with its matching environment base URL. IDs, tokens, prebooking IDs, and booking IDs must also remain in the environment where they were created.

​
Required Headers

​
Keep Credentials Safe

Call Unifystays from your trusted backend. Do not expose API keys in browser code, mobile applications, public repositories, or client-side logs. When rotating a key, deploy the replacement key first, confirm successful traffic, then disable the old key in the portal.

​
Add a Supplier Without Reintegrating

When you need a new supported supplier, enable it and add its credentials in the portal. Your customer-facing integration remains unchanged: it continues to use the same normalized Unifystays endpoints, response model, and booking flow. Continue to the integration flow