Troubleshooting

Common issues with Allez links and how to fix them.

If using /allez/roam: This is expected behavior - roam uses ML to pick the best provider for each user. If you need a specific provider, use /allez/booking, /allez/expedia, etc.

If using a specific provider: Check that the provider name in the URL is correct. Valid values: booking, expedia, hotelscom, vrbo, airbnb, agoda, tripadvisor, kayak, getyourguide.

Hotel not found / wrong hotel

  • Add context: Use hotelname together with address (city + country). Just a hotel name without location may match the wrong property.
  • Check spelling: Hotel name matching uses fuzzy matching (~60% threshold), but very different spellings won't match.
  • Use coordinates: If you have the hotel's lat/lng, pass them via lat and lng - this is more reliable than name matching.
  • Use hotel ID: If you know the provider-specific hotel ID, pass it via hid for a direct lookup.
  • Is the hotel still listed? Check if the listing is still live on the OTA.

Landing on wrong country/TLD

Stay22 routes users based on their IP location. An Australian user clicking a Vrbo link will land on stayz.com.au, not vrbo.com. This is intentional - it improves conversion rates.

If you need to override this, pass lang and currency parameters to hint at the desired locale. See Providers for geo-routing and TLD details.

URL not working / 404

  • Check encoding: Addresses with special characters must be URL-encoded. Use encodeURIComponent() in JavaScript or urllib.parse.quote() in Python.
  • Check link parameter: If using the link parameter, the entire URL must be URL-encoded, not just spaces.
// Correct
const encoded = encodeURIComponent('https://www.booking.com/hotel/fr/le-marais.html');
const url = `https://www.stay22.com/allez/booking?aid=<AID>&link=${encoded}`;

// Wrong - will break
const url = `https://www.stay22.com/allez/booking?aid=<AID>&link=https://www.booking.com/hotel/fr/le-marais.html`;

Dates not pre-filled on the provider page

  • Check the format: dates must be YYYY-MM-DD (e.g., 2026-07-15).
  • Dates must be in the future.

Need help?

Reach out to support@stay22.com or use the chat in hub.stay22.com.

On this page