eDreams APIedreams.it ↗
Search eDreams Italy flights, trains, hotels, and flight+hotel packages via API. Returns prices, itineraries, and availability in EUR.
What is the eDreams API?
The eDreams Italy API exposes 6 endpoints covering flight search, train search, hotel availability, flight+hotel package search, and two autocomplete location lookups. The search_flights endpoint returns full itineraries with per-leg detail, cabin class, seat availability, and both public and eDreams Prime member prices. Prices are denominated in EUR, reflecting the Italian storefront.
curl -X GET 'https://api.parse.bot/scraper/9302b767-695d-4424-af13-083861df5781/search_locations?query=napol&product=TRAIN' \ -H 'X-API-Key: $PARSE_API_KEY'
Typed, relational, agent-ready
A generated client with real types, enums, and the links between objects — the structure a flat JSON response can't carry. Autocompletes in your editor and reads cleanly to coding agents.
- Fully typed · autocompletes
- Objects link to objects
- Typed errors & pagination
Typed Python client. Set up the SDK in your uv project, then pull this API’s typed client:
uv add parse-sdk uv run parse init uv run parse add --marketplace edreams-it-api
uv run parse add --marketplace pulls a pinned snapshot of this canonical API — it won’t change underneath you. To customize it, subscribe and swap to your own copy.
"""Walkthrough: eDreams Italia — search flights, hotels, and packages."""
from parse_apis.edreams_it_api import Edreams, LocationProduct, HotelSort, InputNotFound
client = Edreams()
# Find train stations for a city, then look up flights from the same place.
locations = client.locations.search("Milano", product=LocationProduct.FLIGHT, limit=3)
for loc in locations:
print(loc.name, loc.geo_node_id, loc.iata)
# Search round-trip flights Milan → London.
for flight in client.itineraries.search_flights(
origin="MIL", destination="LON",
departure_date="2026-11-11", return_date="2026-11-14",
limit=5,
):
outbound = flight.legs[0]
print(flight.price, flight.currency, outbound.carrier, f"{outbound.duration_minutes}min")
# Hotel workflow: resolve a destination, then search hotels inside it.
dest = client.hotel_destinations.search("Roma", limit=5).first()
if dest is not None:
print(dest.label, dest.destination_id, dest.region_type)
# Use the typed destination to search hotels — derived identifier flows naturally.
for hotel in dest.hotels.search(
check_in="2026-11-11",
check_out="2026-11-13",
sort=HotelSort.HIGHER_DISCOUNT,
limit=5,
):
print(hotel.name, hotel.stars, hotel.total_price, hotel.currency, hotel.discount_percentage)
# Flight + hotel packages for the same dates.
try:
pkg = client.packages.search(
origin="MIL", destination="LON",
check_in="2026-11-11", check_out="2026-11-14",
limit=1,
).first()
if pkg is not None:
print(pkg.name, pkg.package_price_per_person, pkg.board_type, pkg.free_cancellation)
except InputNotFound as e:
# Unknown IATA code returns input_not_found
print("Route not found:", e.message)
print("exercised: locations.search / itineraries.search_flights / hotel_destinations.search / hotels.search / packages.search")
Looks up airports, cities and train stations by free text, as the flight/train search form autocompletes them. Returns one row per match; a city row carries its airports (product=FLIGHT) or its train stations (product=TRAIN) under related_locations. The geo_node_id of any row (or related row) is the identifier search_flights and search_trains accept as origin/destination; iata is present for airports and cities and can be used instead for flights and packages. Text matching is the site's own, so a short query may also return far-away places (match_type NEAREST). An empty locations array means the site found no match. Single round trip, no pagination.
| Param | Type | Description |
|---|---|---|
| queryrequired | string | Free text, at least 2 characters (city, airport or station name). |
| product | string | Which product's location catalogue to search: FLIGHT returns cities and airports, TRAIN returns cities and train stations. |
{
"type": "object",
"fields": {
"query": "echo of the query",
"product": "echo of the product",
"locations": "array of matches; each has geo_node_id (string, consumed by search_flights/search_trains), iata (nullable), type (CITY | AIRPORT | TRAIN_STATION), match_type (site match class, e.g. CITY, AIRPORT, TRAIN_STATION, NEAREST), name, city, country, country_code, latitude, longitude, distance_km (nullable, set on related rows), related_locations (array of the same shape: airports or stations serving a city)"
},
"sample": {
"data": {
"query": "napol",
"product": "TRAIN",
"locations": [
{
"city": "Napoli",
"iata": "NAP",
"name": "Napoli",
"type": "CITY",
"country": "Italia",
"latitude": 40.846151,
"longitude": 14.25755,
"match_type": "CITY",
"distance_km": null,
"geo_node_id": "2971",
"country_code": "IT",
"related_locations": [
{
"city": "Napoli",
"iata": null,
"name": "Napoli Centrale",
"type": "TRAIN_STATION",
"country": "Italia",
"latitude": 40.852451,
"longitude": 14.273096,
"match_type": "TRAIN_STATION",
"distance_km": 2,
"geo_node_id": "1070191",
"country_code": "IT"
}
]
},
{
"city": "Afragola",
"iata": null,
"name": "Napoli Afragola",
"type": "TRAIN_STATION",
"country": "Italia",
"latitude": 40.931704,
"longitude": 14.331465,
"match_type": "TRAIN_STATION",
"distance_km": null,
"geo_node_id": "110176733",
"country_code": "IT",
"related_locations": []
}
]
},
"status": "success"
}
}About the eDreams API
Location Resolution
Before calling any search endpoint, use search_locations to resolve free-text city, airport, or station names into identifiers. Pass a query string (minimum 2 characters) and a product value — FLIGHT for airports and cities, TRAIN for train stations. Each result carries a geo_node_id (used as origin or destination in flight and train searches), a nullable iata code, and a type field (CITY, AIRPORT, or TRAIN_STATION). City-level results include nested related_locations listing the subordinate airports or stations. For hotels, a separate search_hotel_destinations endpoint handles autocomplete and returns destination_id values consumed by search_hotels.
Flight and Train Search
search_flights accepts an origin and destination (either IATA codes or geo_node_id values), travel dates, passenger counts (adults, children, infants), and an optional cabin_class (TOURIST = economy). Each itinerary in the response includes price (total for all passengers), prime_price (eDreams Prime member price), currency, nullable tickets_left, transport_types, and a legs array with sections detailing individual segments. search_trains follows the same request/response shape but requires geo_node_id values from the TRAIN product catalogue; IATA codes are accepted only at the city level.
Hotel and Package Search
search_hotels takes ISO check_in / check_out dates, destination_id (from search_hotel_destinations), adults per room, optional children_ages as a comma-separated string, and a sort parameter. Each hotel record includes name, type, category (STARS_x), stars, chain, address, neighbourhood, and pricing. search_flight_hotel_packages bundles a round-trip flight with a hotel stay; it takes IATA codes for origin and destination and returns the same hotel-level fields alongside flight pricing — all priced per person. Both search endpoints support limit/offset pagination via the has_more flag.
Pagination and Result Counts
All search endpoints are paginated with limit (1–100), offset, and a has_more boolean. search_flights and search_trains typically surface tens to roughly 1,000 itineraries per search; search_hotels and search_flight_hotel_packages can return 1,000–3,000 properties for major cities. search_id is included on every search response and identifies the site-side result set.
The eDreams API is a managed, monitored endpoint for edreams.it — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when edreams.it changes and a check fails, the API is automatically queued for repair and re-verified. It is built to keep working as the site underneath it changes.
This isn't an official edreams.it API — it's an independent, maintained REST wrapper over public data. Where the source has no official API (or only a limited one), Parse gives you a stable contract over a source that never promised one, and keeps it current. Need a new endpoint or field? You can revise it yourself in plain English and the agent rebuilds it against the live site in minutes — contributing the change back to the shared API is free.
Will this API break when the source site changes?+
Is this an official API from the source site?+
Can I fix or extend this API myself if I need a new endpoint or field?+
What happens if I call an endpoint that has an issue?+
- Aggregate flight prices between Italian cities and European hubs using
search_flightsitinerary data. - Compare eDreams public prices against
prime_priceto quantify the membership discount across routes. - Monitor
tickets_lefton specific flight legs for seat-scarcity signals. - Build a city-pair train fare tracker using
search_trainswith station-levelgeo_node_idvalues. - Populate a hotel availability feed for a given destination using
search_hotelswithcheck_in/check_outdates. - Find combined flight+hotel package prices for a destination using
search_flight_hotel_packagespriced per person. - Drive a location autocomplete UI backed by
search_locationsIATA andgeo_node_idresolution.
| Tier | Price | Credits/month | Rate limit |
|---|---|---|---|
| Free | $0/mo | 200 | 5 req/min |
| Hobby | $30/mo | 1,000 | 20 req/min |
| Developer | $100/mo | 5,000 | 100 req/min |
| Team | $300/mo | 20,000 | 300 req/min |
| Company | $1,000/mo | 100,000 | 500 req/min |
Each endpoint has a fixed posted price per successful call — most fall between 1 and 10 credits — shown on this API's page before you run it. Exceeding the rate limit returns a 429 response. Authenticate with the X-API-Key header.
Does eDreams have an official public developer API?+
What does `search_flights` return for each itinerary, and how does it differ from `search_trains`?+
search_flights returns itineraries filtered to all-plane legs. Each itinerary includes price, prime_price, currency, tickets_left (nullable), transport_types, and a legs array with per-section detail. search_trains returns the same shape but covers rail itineraries; origin and destination must be geo_node_id values from the TRAIN product catalogue, and only TOURIST (standard class) cabin has been exercised.Can I retrieve individual seat-map or fare-rule details for a specific flight?+
tickets_left, but not seat maps, baggage rules, or fare conditions. You can fork the API on Parse and revise it to add an endpoint targeting that detail.How does pagination work across the search endpoints?+
limit (1–100 results per page) and offset (zero-based). Each search response includes a has_more boolean that is true when offset + limit is less than total_results. Increment offset by limit to walk through subsequent pages. The search_id field in each response identifies the underlying result set.