Despegar Scraper | Hotels Flights Packages LatAm avatar

Despegar Scraper | Hotels Flights Packages LatAm

Pricing

from $2.20 / 1,000 results

Go to Apify Store
Despegar Scraper | Hotels Flights Packages LatAm

Despegar Scraper | Hotels Flights Packages LatAm

Scrape Despegar LatAm hotels, flights, suggestions & packages. Extract prices, ratings, hotel IDs & offer URLs across AR/MX/CO and more. Export Excel/CSV/JSON. Unofficial — not affiliated with Despegar.

Pricing

from $2.20 / 1,000 results

Rating

0.0

(0)

Developer

kane liu

kane liu

Maintained by Community

Actor stats

1

Bookmarked

1

Total users

0

Monthly active users

2 days ago

Last modified

Share

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?

DataSuggestionsHotels searchHotel detail*Flights searchPackages 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 (+ enrichLimit) 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.


More Actors like this

Need another travel OTA or a different vertical? Use a dedicated Actor below for structured fields. Use this Actor for Despegar LatAm hotels, flights, suggestions, and packages.

Similar travel & stays Actors

Prefer another specialized scraper?

If your target has a specialized Actor below, use that first — usually cheaper and more structured than a generic scrape.

Jobs & Freelance

E-commerce

Real Estate

Social & Content

Ads Intelligence

Local & Maps

General Tools

→ See the full catalog in Related Actors below, or browse apify.com/lentic_clockss.


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:

EventPrice
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 collectedApprox. 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)

CapValue
Free Apify-plan runs of this Actor10 total
Free results / run200
Paying Apify usersUnlimited 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:

FieldDescription
modesuggestions, hotelsSearch, hotelDetail, flightsSearch, packagesSeo (plus unsupported waivers)
countrySiteLatAm host such as despegar.com.ar (default), .mx, .co, .cl, .br, .pe, .ec, .uy
queryCity / place text for suggestions or hotel search
destinationGidOptional Despegar GID (e.g. CIT_982) to skip suggestions lookup
hotelIdRequired for hotelDetail
checkin / checkoutStay dates (YYYY-MM-DD)
origin / destinationFlight / packages route fields
tripTyperoundtrip or oneway for flights
maxResultsCap on emitted Dataset rows
enrichDetailsEnrich hotel search hits with detail pages
enrichLimitBounded detail enrichment count
workerBaseUrlAdvanced 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:

FieldDescription
mode / countrySiteCollection mode and Despegar host
name / title / displayHotel, offer, or suggestion label
hotelId / gidDespegar identifiers when present
priceText / currency / scorePricing and rating signals
productUrlPublic product / offer URL
origin / destinationRoute fields for flights / packages
checkin / checkoutStay dates
capturedAtCapture timestamp

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

Lead / contact fields

Every Dataset item keeps the existing Despegar business fields and includes the complete Lead shape below. Empty or unavailable values are kept explicit through leadAbsences; a missing value is not presented as a discovered contact.

FieldTypeDespegar meaning and measured source
phones[{value, type, e164?}]Phone, landline, mobile, or WhatsApp contacts. The opened Suggestions JSON returned none, so those rows use [] and leadAbsences.phones=本站无(Suggestions opened payload 未返回电话).
emails[{value, type}]Contact email addresses. The opened Suggestions JSON returned none, so those rows use [] with the corresponding 本站无 reason.
address{street, unit, locality, region, postalCode, country, full}Structured address. unit means the street/door number. Suggestions can populate parent locality, region, and country, but do not expose street, unit, postal code, or full address.
geo{lat, lng} or nullNumeric coordinates from Suggestions location.latitude and location.longitude when both exist. Coordinates supplement an address; they do not prove a street or door number.
person{name, role?} or nullAn individual contact such as a host, agent, owner, or representative. Lodging businesses belong in org, not person; no individual was present in the opened Suggestions payload.
org{name, id?} or nullFor lodging Suggestions (HOTEL / VACATION_RENTAL), the organization name is the full visible suggestion label and the ID is the Despegar GID/item ID. The accepted sample included HOT_4046444 / Platinum Hotel, Rajkot, India.
web{website, socials[]}Entity-owned website and social links. The opened Suggestions payload exposed neither; Despegar platform support links are not treated as hotel leads.
leadSourcesearch | detail | entity | contact | reveal-xhrentity for lodging Suggestions, search for non-lodging Suggestions, and the matching surface for other modes when that surface produces a row.
leadRevealvisible | click | xhr | gated | image | absentThe accepted Suggestions rows use visible: one guest-visible JSON request, with no reveal click. Gated shopping/detail surfaces are not reported as visible leads.
leadAbsencesobject/mapPer-field reason for unavailable data. Reasons distinguish 本站无 on the opened Suggestions payload from 闸门锁 / 未验证 on shopping and detail surfaces that were not opened successfully.

The successful acceptance run was fcHf6CQgwhJYdVJrg (Actor build 0.1.17, Dataset 2NketDH1OZ0rVkzyd, three rows). All three rows contained every Lead key. This documents that measured run and does not imply that every mode exposes the same contact data.

Reveal cost

  • Suggestions: no click reveal, login, agent page, or hotel-detail visit is required. Each acquisition attempt performs one direct same-origin Suggestions JSON fetch in its inherited browser session. The current worker can make up to three bounded proxy-session attempts after acquisition/browser errors; there is no pagination.
  • Hotel search/detail enrichment: enrichDetails can add a bounded number of detail visits for hotel results. Each detail visit adds run time and proxy/browser work. The 2026-09-08 acceptance did not exercise this path because the measured shopping/detail documents were challenge-gated.
  • Phone/email reveal: no click-to-show or reveal XHR was found on the opened Suggestions surface, so the worker does not make an extra reveal request for those rows. It does not submit login, booking, payment, or contact forms.
  • Keep maxResults and enrichLimit small when testing. Increasing them can increase page visits, duration, proxy usage, and exposure to rate limits or anti-bot gates.

Honest limitations

  • The 2026-09-08 accepted live path is MX Suggestions. AR/MX Suggestions expose lodging organization identities and sometimes coordinates/parent geography, but not phone, email, street/door number, person, entity website, or social links.
  • Suggestions preserve the first ranked item but, when maxResults >= 2 and that capped slice has no lodging entity, the worker replaces its last row with the first later HOTEL / VACATION_RENTAL result. This protects the measured lodging lead from truncation, but the inserted lodging can be geographically unrelated to the query, as shown by the Rajkot hotel in the Ciudad de México acceptance.
  • Suggestions parent geography may be raw Despegar identifiers such as CIT_..., ADM_..., or COU_... instead of human-readable locality, region, or country text. The Actor preserves the returned value rather than guessing a label.
  • AR Home, Hotels Search, Hotel Detail, Flights Search, and Packages SEO were blocked by DataDome/Cloudflare challenge or non-business loading shells during the current recon. Rows produced by code-side parsers for those surfaces use honest 闸门锁 / 未验证 absence reasons; challenge-page text is never treated as contact data.
  • MX shopping applications beyond Suggestions were not live-validated in this acceptance. Country-site support in the input schema does not guarantee identical shopping behavior on every Despegar TLD.
  • cars, transfers, and activities remain explicit unsupported-mode waivers. They fail clearly instead of returning a fake empty success.
  • Source .actor/actor.json sets default and maximum run memory to 1024 MB (minimum 512 MB), and the accepted run was explicitly started with 1024 MB. The Apify Actor API may still report defaultRunOptions.memoryMbytes=512; do not treat that control-plane value as proof that the source setting or accepted run used 512 MB.

Coverage matrix

DimensionCoverage
Country sitesdespegar.com.ar (default) + MX / CO / CL / BR / PE / EC / UY hosts in schema
Modes shippedsuggestions · hotelsSearch · hotelDetail · flightsSearch · packagesSeo
Waiverscars / 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.

Source default run memory: 1024 MB (min 512, max 1024). The accepted build 0.1.17 run used 1024 MB explicitly. The Apify Actor API may temporarily continue to report defaultRunOptions.memoryMbytes=512; see Honest limitations.


Run artifacts

KeyPurpose
INPUT_ECHONormalized non-secret input and resolved worker source
RUN_SUMMARYWorker, proxy source, free-tier, and record metrics
ERROR_SUMMARYStructured 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.


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.


All 77 public Actors from [lentic_clockss]. Click a name to open the Store detail page.

Jobs & Freelance

Real Estate

E-commerce

Travel & Stays

Social & Content

Ads Intelligence

Local & Maps

General Tools

→ Browse the full profile: apify.com/lentic_clockss