Travel Search

Search for flights, tours, and excursions with real prices and booking links.

Available tools

Run the HTTP client to call APIs:

CODEBLOCK0

INLINECODE0, --body, and --headers must be valid JSON objects. Do not pass query strings like a=1&b=2.

1. Flights (Aviasales)

Cached flight prices. Read references/aviasales-data-api.md for all endpoints and parameters.

Quick example — cheapest flights:
CODEBLOCK1

After getting prices, create a booking link on aviasales.ru. See references/aviasales-links.md for URL format, then get a short link:
CODEBLOCK2

2. Tours (Travelata)

Package tours (flight + hotel). Read references/travelata-api.md for all parameters and search strategy. Use references/travelata-directories.md only if you need to look up IDs.

Important: The API returns one cheapest tour per check-in date. Always search a date range (±7 days), never a single day. If strict filters return 0, retry without filters first, then widen the date range.

Quick example — cheapest tours in Turkey, 7 nights around June 15:
CODEBLOCK3

The response includes hotelName, hotelRating, hotelCategoryName, and tourPageUrl directly. Convert tourPageUrl through /short-link:
CODEBLOCK4

3. Excursions (Sputnik8)

Read references/sputnik8-api.md for endpoints.

Quick example — excursions in Kemer:
CODEBLOCK5

4. Utilities

• - City/airport lookup: references/travelpayouts-utils.md — autocomplete and IATA resolver
• Short links: GET https://api.botclaw.ru/short-link?url=<URL> — get a short booking link for any travel URL
• Airline logos: http://pics.avs.io/{width}/{height}/{IATA}.png (e.g. http://pics.avs.io/200/200/SU.png)
• Currency rates to RUB: INLINECODE13

Workflow

1. 1. Resolve locations — if user says city names, use the autocomplete or IATA resolver to get IATA codes (for flights). For tours, resolve the country first. Only narrow to a specific Travelata resort when the user explicitly asks for an exact area such as Kemer, Belek, Side, or Alanya. For package-tour requests like "Antalya", start broad with Turkey (countries[]=92) because users often mean the Antalya coast, not only the exact municipality.
2. Search — call the appropriate API(s) based on user request
3. Get short links — convert result URLs via INLINECODE15
4. Present results — show prices, hotel names, ratings, and booking links

Rules

• - ALWAYS convert ALL URLs to short links via /short-link before showing to users — this applies to Aviasales, Travelata, AND Sputnik8 links. Never show raw URLs from API responses directly.
• For flights: show cached prices from Data API + link to full search on aviasales.ru
• For tours: default to 4-5 star, all-inclusive, rating 4+. Always search a date range (±7 days from requested date), never a single day. Show hotel name, stars, meal, price, check-in date, and booking link.
• For tours: if strict filters return 0, retry WITHOUT filters first (same dates and tourists), then widen date range. Only say "no tours" if the unfiltered search is also empty.
• For tours: if results are few (under 3) or none match the user's preferences well, recommend checking more options on these services:

• - For tours with a budget: if results exceed budget, present the cheapest options clearly marked as "above budget".
• For tours with an exact area request: pass resorts[] (array format). Verify the returned resortId field in each result.
• For combined requests (flights + tours): search both and compare
• Prices from Data API are cached (2-7 days old) — mention this to users. If no data found for requested dates, the API automatically returns nearest available dates.
• When user asks for tours plus excursions, always search Sputnik8 too, even if tour results are empty or only slightly above budget.
• When showing flight or tour results, suggest searching for activities and excursions at the destination via Sputnik8 (e.g. "Want me to find excursions and things to do in Antalya?")