Despegar Scraper — Hotels, Flights & Packages (LatAm)

Scrape Despegar hotel search, hotel detail, flight search, destination suggestions, and packages SEO pages across Latin American Despegar sites — then download structured results as Excel, CSV, or JSON.

Use this Actor as a practical Despegar hotels / flights data API for LatAm price monitoring, OTA competitive research, and travel lead enrichment. Pick a country site (default despegar.com.ar), choose a mode, enter a destination or route, and get Dataset rows with names, prices, scores, product URLs, and trip metadata.

• Scrape Despegar hotel search by city / destination (with optional hotel-detail enrichment)
• Collect flight search offers (one-way / round-trip style routes)
• Resolve destinations via suggestions (GID lookup)
• Pull packages SEO landing signals where supported
• Cover LatAm hosts such as Argentina, Mexico, Colombia, Chile, Brazil, Peru, Ecuador, Uruguay
• Export to Excel / CSV / JSON, or connect Make, n8n, Zapier, Python, or the Apify API
• Pay per event — Actor start + each Dataset result; platform usage is included (you do not pay separate Apify compute on top)

Unofficial tool. This Actor is not affiliated with, endorsed by, or sponsored by Despegar.com Corp or Despegar brand sites. It collects publicly reachable shopping / SEO surfaces and does not complete bookings or access private accounts.

---

What does the Despegar Scraper do?

Despegar Scraper lets you extract structured travel inventory from Despegar LatAm OTAs without operating your own anti-bot browser fleet. Give it a destination (for example Buenos Aires), dates, and a mode, then start a run.

Under the hood, the Actor:

1. Validates your input (mode, country site, destination / route, dates, enrichment flags)
2. Enforces free-tier caps when you are on a free Apify plan
3. Calls a managed Cloud Run worker (despegar-com) that opens shopping pages with residential egress
4. Parses guest-visible hotel / flight / suggestion / packages signals into normalized records
5. Pushes Dataset rows ready for Excel / CSV / JSON export
6. Writes RUN_SUMMARY (and ERROR_SUMMARY on failure) to the key-value store

You run it like any other Apify Actor — schedule it, call it from the API, or plug it into automations.

---

What Despegar data can I extract?

Data	Suggestions	Hotels search	Hotel detail*	Flights search	Packages SEO
Destination / GID / display	✅	✅	—	—	✅
Hotel name / hotelId	—	✅	✅	—	—
Price text / currency	—	✅	✅	✅	✅
Score / rating signals	—	✅	✅	—	—
Product / offer URL	—	✅	✅	✅	✅
Check-in / check-out	—	✅	✅	—	—
Origin / destination / trip type	—	—	—	✅	✅
Country site	✅	✅	✅	✅	✅

*Enable enrichDetails (+ maxDetailHotels) to visit a bounded number of hotel detail pages after search.

Not shipped as successful scrapes (schema waivers): cars, transfers, activities — selecting these returns a clear failure instead of fake empty success.

---

Why scrape Despegar?

Despegar is one of the largest online travel platforms in Latin America. Teams scrape Despegar to:

• Monitor hotel prices and availability by city and stay dates
• Compare flight offer signals for popular LatAm routes
• Enrich catalogs with destination GIDs from suggestions
• Track packages SEO landing content for market research
• Feed BI dashboards, pricing tools, or AI agents with structured LatAm OTA rows

Compared with Despegar Actors that only collect hotel reviews or a single-country hotel SERP, this Actor covers hotels + flights + suggestions + packages SEO across multiple LatAm country sites in one input surface.

---

How to scrape Despegar (no code required)

1. Create a free Apify account
2. Open Despegar Scraper
3. Choose a mode: hotelsSearch (default), hotelDetail, flightsSearch, suggestions, or packagesSeo
4. Choose a country site (default despegar.com.ar)
5. Enter a query / destination (hotels) or origin + destination (flights)
6. (Optional) Set checkin / checkout, enrichDetails, or destinationGid
7. Click Start and download the Dataset as JSON, CSV, Excel, or JSONL

Start with maxResults: 5–10 to verify the query, then scale up.

---

How much does it cost to scrape Despegar?

This Actor uses pay-per-event pricing. You are charged for:

Event	Price
Actor Start (apify-actor-start)	$0.005 per start
Result (apify-default-dataset-item)	$3.00 / 1,000 results ($0.003 each)

Platform usage costs are included — you do not pay separate Apify compute/proxy usage for this Actor on top of the event prices above.

Example cost estimates

Results collected	Approx. event cost*
100	~$0.31
1,000	~$3.01
10,000	~$30.01

*Assumes one Actor start at default memory billing for start events, plus $0.003 per Dataset item. Exact start billing can scale with allocated memory (one start event per GB, minimum one).

Free Apify trial credit can cover a small test run — try maxResults: 5 first.

Free-tier caps (Actor developer limits)

Cap	Value
Free Apify-plan runs of this Actor	10 total
Free results / run	200
Paying Apify users	Unlimited runs (schema max still applies)

These limits are enforced in Actor code (set by the Actor developer, not Apify). When the run cap is hit, the Actor finishes successfully with RUN_SUMMARY.status = FREE_TIER_LIMIT and a clear status message.

---

Input

Open the Input tab for the full form. Common fields:

Field	Description
mode	suggestions, hotelsSearch, hotelDetail, flightsSearch, packagesSeo (plus unsupported waivers)
countrySite	LatAm host such as despegar.com.ar (default), .mx, .co, .cl, .br, .pe, .ec, .uy
query	City / place text for suggestions or hotel search
destinationGid	Optional Despegar GID (e.g. CIT_982) to skip suggestions lookup
hotelId	Required for hotelDetail
checkin / checkout	Stay dates (YYYY-MM-DD)
origin / destination	Flight / packages route fields
tripType	roundtrip or oneway for flights
maxResults	Cap on emitted Dataset rows
enrichDetails	Enrich hotel search hits with detail pages
maxDetailHotels	Bounded detail enrichment count
workerBaseUrl	Advanced allowlisted worker override (optional)

Input example

{
  "mode": "hotelsSearch",
  "countrySite": "despegar.com.ar",
  "query": "Buenos Aires",
  "checkin": "2026-08-20",
  "checkout": "2026-08-24",
  "maxResults": 20,
  "enrichDetails": false
}

---

Output

Each Dataset item includes mode / site metadata plus fields such as:

Field	Description
mode / countrySite	Collection mode and Despegar host
name / title / display	Hotel, offer, or suggestion label
hotelId / gid	Despegar identifiers when present
priceText / currency / score	Pricing and rating signals
productUrl	Public product / offer URL
origin / destination	Route fields for flights / packages
checkin / checkout	Stay dates
capturedAt	Capture timestamp

Field presence depends on mode and what the public page exposes for that run.

---

Coverage matrix

Dimension	Coverage
Country sites	despegar.com.ar (default) + MX / CO / CL / BR / PE / EC / UY hosts in schema
Modes shipped	suggestions · hotelsSearch · hotelDetail · flightsSearch · packagesSeo
Waivers	cars / transfers / activities — clear error only (no fake success)

Notes: SEO paths like /hoteles/hl|h- are marketing landings and are not the same as priced shopping SERP/PDP. Prefer shopping modes (hotelsSearch / hotelDetail) for offer-like prices.

---

Architecture and proxy ownership

Apify Actor (input, Dataset, free tier, Standby, PPE)
        │ HTTPS + WORKER_AUTH
        ▼
Cloud Run worker despegar-com (Patchright session, parse, OpenAPI)
        ▼
Despegar LatAm public shopping / SEO pages

WORKER_PROVIDES_PROXY=1 is enabled by default. The Actor does not mint or transmit proxyUrl; proxy/egress is configured on the worker (including egress-control). Set WORKER_BASE_URL and secret WORKER_AUTH in Actor settings.

Default run memory: 1024 MB (min 512).

---

Run artifacts

Key	Purpose
INPUT_ECHO	Normalized non-secret input and resolved worker source
RUN_SUMMARY	Worker, proxy source, free-tier, and record metrics
ERROR_SUMMARY	Structured failure before valid records are emitted

---

Integrations & API

• Schedule recurring Despegar hotel / flight pulls from Apify Console
• Call the Actor from Python, Node.js, or curl via the Apify API
• Connect to Make, n8n, Zapier, Google Sheets, or your BI stack

API example

curl -X POST "https://api.apify.com/v2/acts/lentic_clockss~despegar-scraper/runs?token=$APIFY_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "mode": "hotelsSearch",
    "countrySite": "despegar.com.ar",
    "query": "Buenos Aires",
    "maxResults": 20
  }'

---

FAQ

Is login required?

No. The Actor targets publicly reachable shopping / SEO surfaces via the managed worker.

Can it book hotels or flights?

No. Booking, payment, and account flows are intentionally excluded.

Why is my SEO hotel URL different from search results?

Despegar SEO hotel landings (/hoteles/hl|h-) are not the same stack as priced accommodations shopping results. Use hotelsSearch / hotelDetail for offer-oriented extraction.

Do cars, transfers, or activities work?

Not yet. Those modes are schema placeholders and fail with an explicit unsupported-mode error.

Do I pay Apify platform usage separately?

No for this Actor’s configured PPE plan — User pays platform usage costs = No. You pay the event prices above; platform usage is covered by the Actor developer.

---

Legal & responsible use

Use this Actor only for lawful purposes and in line with Despegar terms and applicable laws. You are responsible for how you store and use the data. Prefer low-volume smoke inputs first (maxResults: 2–5).

---

Support

Questions or feature requests: open an issue on the Actor page in Apify Console or contact the developer through Apify.