Developer resources

Bileteavia Flight Search API for AI assistants

A read-only interface for searching current flight options and handing travellers back to Bileteavia with their route, dates and passenger count already prepared.

Read-only search API v1 EUR

Current search observations

Flight routes, times, airline codes and availability status are normalized from the provider response for the requested dates.

Customer-facing prices

Every amount passes through the current Bileteavia admin ticket adjustment rules. The API does not expose the provider base fare or the adjustment value.

Safe transaction boundary

Searching does not create a session, lead, reservation, payment, email or Discord notification. A separate website flow is required to reserve.

HTTP contract

Search endpoint and parameters

Send a GET request with IATA airport codes and an eligible departure date. Unknown parameters are rejected so integrations cannot silently send unsupported travel data.

GET https://bileteavia.md/api/v1/flights/search?origin=RMO&destination=CDG&departureDate=YYYY-MM-DD&passengers=1&currency=EUR
Parameter Required Meaning
origin Yes Three-letter origin IATA code.
destination Yes Three-letter destination IATA code, different from origin.
departureDate Yes Departure date in YYYY-MM-DD format, from today through 370 days ahead.
returnDate No Optional return date after departure and within 370 days.
passengers No Adult passenger count from 1 to 9; defaults to 1.
cabin No economy or business; defaults to economy.
currency No EUR only in version 1, so fixed admin adjustments remain currency-correct.
baggage No any only; baggage inclusion is reported as not confirmed.

What a successful response means

The JSON response is designed for assistants to describe options accurately without turning a search observation into a booking promise.

  • The price amount is in EUR, includes the applicable admin adjustment and is marked indicative.
  • Availability records when the option was observed and always requires a recheck.
  • Outbound and optional return legs include airports, times, duration, stops and airline codes when supplied by the provider.
  • continue_search_url opens a new customer-facing search on Bileteavia with the normalized request state.
Price and availability are not guaranteed Bileteavia rechecks the selected option before reservation. An assistant must not claim that a seat is booked or that a displayed fare is final.

Connecting the endpoint to Gemini

Gemini does not automatically execute an API discovered in Google Search. The integrating application controls tool execution.

  1. 1Load the published Gemini function declaration and include it in the tools sent to the Gemini API.
  2. 2When Gemini returns search_bileteavia_flights, validate its arguments and call the Bileteavia GET endpoint with those query parameters.
  3. 3Return the API JSON to Gemini and show continue_search_url to the traveller as the next action.

The public declaration is integration metadata, not automatic registration with Google or a guarantee of inclusion in AI Overviews or AI Mode.

Continue on Bileteavia

The API supports discovery and comparison. The website remains the customer-facing place to recheck an option and continue toward a reservation.

Search flights

Flight Search API questions

Will Google AI automatically call this API?

No. Google Search may index and cite this documentation page, but a Gemini application must explicitly register the function and execute the API call.

Do returned prices include Bileteavia admin adjustments?

Yes. The public amount already includes the applicable ticket-price adjustment configured in Bileteavia admin, but it remains indicative and requires a recheck.

Does an API search create a lead or reservation?

No. Searching is read-only and does not create a session, CRM lead, Discord notification, reservation, payment or email.