Providers

Each provider endpoint handles the redirect to a specific OTA. Use /allez/roam to let the AI pick the best one, or target a provider directly.

Accommodation providers

Booking.com

Endpoint: /allez/booking

The most widely available provider globally. Supports hotel IDs, deep links, and address-based search.

Geo routing: Booking.com uses a single TLD (booking.com) internationally, but Stay22 automatically sets the correct language and currency based on the user's location.

Expedia

Endpoint: /allez/expedia

Supports 30+ regional TLDs. Stay22 automatically routes users to the correct one (e.g., expedia.ca, expedia.co.uk, expedia.de).

Hotels.com

Endpoint: /allez/hotelscom

Part of the Expedia Group. Includes regional subdomains like hoteles.com (LATAM) and hoteis.com (Brazil). All handled automatically.

Vrbo

Endpoint: /allez/vrbo

Focused on vacation rentals. Has the most complex geo-routing of any provider:

User location	Redirected to
US / International	vrbo.com
France	abritel.fr
Australia	stayz.com.au
New Zealand	bookabach.co.nz
Germany	fewo-direkt.de

Even if you hard-code a vrbo.com link, an Australian user will land on stayz.com.au with the same listing.

Airbnb

Endpoint: /allez/airbnb

Supports address-based search and hotel name matching.

Agoda

Endpoint: /allez/agoda

Strong inventory in Asia-Pacific markets.

TripAdvisor

Endpoint: /allez/tripadvisor

Supports 30+ regional TLDs (e.g., tripadvisor.fr, tripadvisor.ca, tripadvisor.co.uk). Routed automatically based on user location.

Other providers

Kayak

Endpoint: /allez/kayak

Metasearch engine. Supports all Kayak TLDs as well as sister sites: Momondo, HotelsCombined, Cheapflights, Swoodoo, checkfelix, and Mundi. The correct regional variant is selected automatically.

GetYourGuide

Endpoint: /allez/getyourguide

Activities and experiences. Use the address parameter to search for activities near a destination.

Geo-routing

Stay22 automatically handles geo-routing for every redirect. You don't need to build different links for different regions - one URL works globally.

When a user clicks an Allez link, Stay22 detects their location via IP and redirects them to the correct regional version of the OTA. This happens transparently - you always link to stay22.com/allez/{provider}, and Stay22 handles the rest.

Language and currency

Even when a provider uses a single TLD (like Booking.com), Stay22 passes the correct language and currency based on the user's location. You can also set these explicitly:

https://www.stay22.com/allez/booking?aid=<AID>&address=paris&lang=fr&currency=EUR

If you set lang or currency, they override the auto-detected values.

Hotel name matching

When you pass the hotelname parameter, Stay22 performs fuzzy matching across its hotel database:

https://www.stay22.com/allez/roam?aid=<AID>&address=miami&hotelname=four%20seasons

The matching process:

Searches provider databases (Booking.com, Expedia, Hotels.com, Agoda)
Uses fuzzy string matching with a ~60% similarity threshold
Resolves the hotel's provider-specific ID for a direct deep-link

Tip

Combine hotelname with address (city + country) for the best match accuracy. Just a hotel name without location context may return unexpected results.

Provider selection by endpoint

Endpoint	What happens
`/allez/roam`	AI picks the best provider per user. Learn more.
`/allez/booking`	Always goes to Booking.com
`/allez/expedia`	Always goes to Expedia (with geo TLD)
`/allez/{provider}`	Always goes to the named provider