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

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.
Sandbox does not have Production inventory. It only covers the test cities listed below. Searching anywhere else in Sandbox returns no destinations or no hotels, even when your key and request are correct.

​
Sandbox test cities

Sandbox is meant for building and testing your integration, not for checking coverage. It holds about 1,700 hotels in these cities: Neighborhoods, districts and hotels inside these cities can also be searched. When you test in Sandbox:
  • Pick one of the cities above. If you search for another city (London, Singapore, Mumbai, …), Sandbox returns an empty list. That is expected and does not mean your integration is broken.
  • Take IDs from Sandbox itself. Call Destination Autocomplete against Sandbox and use the IDs it returns. A place or hotel ID copied from Production may not exist in Sandbox.
  • Expect fewer hotels and rates than Production. Prices and availability come from your suppliers’ test systems, so some dates or hotels may return no rates. If that happens, try other dates or another hotel in the same city.
  • Check coverage in Production. Passing in Sandbox shows that your integration works. It does not show which hotels you can sell. See the Launch Checklist.
Need a specific city in Sandbox for your tests? Contact support@unifystays.com.

​
Request Headers

The full header reference is on the Overview.
A key used on the wrong environment returns 403 API_ENVIRONMENT_MISMATCH. Requests are limited per key; see Rate limits.

​
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. Next: run the Quickstart, then read the Hotel Booking Flow and the Launch Checklist.