Current search observations
Flight routes, times, airline codes and availability status are normalized from the provider response for the requested dates.
Developer resources
A read-only interface for searching current flight options and handing travellers back to Bileteavia with their route, dates and passenger count already prepared.
Flight routes, times, airline codes and availability status are normalized from the provider response for the requested dates.
Every amount passes through the current Bileteavia admin ticket adjustment rules. The API does not expose the provider base fare or the adjustment value.
Searching does not create a session, lead, reservation, payment, email or Discord notification. A separate website flow is required to reserve.
HTTP contract
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¤cy=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. |
The JSON response is designed for assistants to describe options accurately without turning a search observation into a booking promise.
Gemini does not automatically execute an API discovered in Google Search. The integrating application controls tool execution.
The public declaration is integration metadata, not automatic registration with Google or a guarantee of inclusion in AI Overviews or AI Mode.
The API supports discovery and comparison. The website remains the customer-facing place to recheck an option and continue toward a reservation.
No. Google Search may index and cite this documentation page, but a Gemini application must explicitly register the function and execute the API call.
Yes. The public amount already includes the applicable ticket-price adjustment configured in Bileteavia admin, but it remains indicative and requires a recheck.
No. Searching is read-only and does not create a session, CRM lead, Discord notification, reservation, payment or email.