Com APIdespegar.com.ar ↗
Access Despegar.com.ar flight search, destination autocomplete, and home travel offers via API. Returns pricing in ARS/USD, IATA codes, airline data, and itineraries.
What is the Com API?
The Despegar.com.ar API exposes 3 endpoints covering destination autocomplete, homepage travel offers, and flight search for the Argentine market. The search_flights endpoint returns full itineraries with airline details, per-segment routing, and prices denominated in both ARS and USD. Results include IATA codes, booking links, and passenger breakdowns for adults, children, and infants.
curl -X GET 'https://api.parse.bot/scraper/d3bd51e8-9d60-468e-ba59-fa852e640ab4/autocomplete?q=buenos&query=miami' \ -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 despegar-com-ar-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.
"""Despegar.com.ar flight search workflow: autocomplete, browse offers, search flights."""
from parse_apis.despegar_com_ar_api import Despegar, FlightSearchFailed
client = Despegar()
# Resolve a city name to IATA codes via autocomplete
airport = client.airportsuggestions.search(query="miami", limit=3).first()
if airport:
print(airport.display, airport.iata, airport.latitude, airport.longitude)
# Browse current travel offers (packages, flights, hotels)
for offer in client.traveloffers.list(limit=3):
print(offer.offer_type, offer.main_text, offer.section)
# Search flights BUE → MIA with typed error handling
try:
flight = client.flights.search(
origin="BUE",
destination="MIA",
departure_date="2026-08-01",
return_date="2026-08-10",
adults=1,
limit=1,
).first()
if flight:
print(flight.airlines[0].name, flight.offer_card_type)
for itin in flight.itineraries:
seg = itin.segments[0]
print(itin.flight_type, seg.from_, seg.to, seg.departure_datetime)
except FlightSearchFailed as exc:
print(f"Flight search failed for {exc.origin} → {exc.destination}: {exc}")
print("exercised: airportsuggestions.search / traveloffers.list / flights.search")
Returns autocomplete suggestions for airports and cities based on a search query. Each suggestion includes the IATA code, geographic coordinates, parent geography (continent, country, city), and a display name in Spanish with HTML highlights on the matched portion. Use to resolve free-text city/airport input into an IATA code suitable for search_flights.
| Param | Type | Description |
|---|---|---|
| queryrequired | string | Search text for airports or cities (e.g. 'miami', 'buenos'). |
{
"type": "object",
"fields": {
"items": "array of airport/city suggestion objects with id, target (iata, type, parents), display name, highlight, and location coordinates"
}
}About the Com API
Endpoints Overview
The API covers three distinct functions. autocomplete accepts a free-text query parameter (e.g. 'miami' or 'buenos') and returns an array of airport and city suggestion objects, each carrying an IATA code, geographic coordinates, a Spanish-language display name, and structured parent location data. This is the correct entry point for resolving user input to an IATA code before calling search_flights.
Flight Search
search_flights requires origin, destination, and departure_date (YYYY-MM-DD). Optionally supply return_date for round trips, and adults, children, or infants for passenger counts. The response includes a flights array where each object carries price, airlines, itineraries (with individual segments), origin, destination, link, and drivers. Note that results represent flight suggestions around the departure date rather than an exact-date fare list — dates close to the requested date are included.
Home Offers
get_home_offers takes no parameters and returns the current promotional listings from the Despegar.com.ar offers surface. Each offer object includes offer_type (flight, package, hotel), main_text, auxiliary_text, a dual-currency price field in ARS and USD, a link for booking, a picture URL, and a section label. The total field tells you how many offers are in the current response.
Coverage Notes
All content is oriented toward the Argentine market: display names are in Spanish, prices default to ARS, and IATA suggestions reflect Despegar's regional catalogue. The search_flights endpoint surfaces round-trip results when return_date is supplied and one-way results when it is omitted.
The Com API is a managed, monitored endpoint for despegar.com.ar — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when despegar.com.ar 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 despegar.com.ar 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?+
- Build a flight price tracker for routes departing from Buenos Aires (AEP, EZE) to major South American hubs
- Populate a destination search input with Spanish-language airport and city suggestions using the autocomplete endpoint
- Aggregate current ARS/USD promotional fares from Despegar's home offers for a travel deals newsletter
- Compare round-trip vs one-way pricing by calling search_flights with and without return_date
- Resolve city or airport names to IATA codes before submitting structured flight search queries
- Display airline names and layover segments for a given origin-destination pair in a travel planning tool
- Monitor offer_type distribution (flights vs packages vs hotels) across Despegar's active promotions
| Tier | Price | Credits/month | Rate limit |
|---|---|---|---|
| Free | $0/mo | 100 | 5 req/min |
| Hobby | $30/mo | 1,000 | 20 req/min |
| Developer | $100/mo | 5,000 | 100 req/min |
One credit = one API call regardless of which marketplace API you call. Exceeding the rate limit returns a 429 response. Authenticate with the X-API-Key header.