Decolar Travel Data: Access and Feasibility

Decolar Scraper & Travel Data Access Options

Researching a Decolar scraper for hotel prices, flight fares, vacation packages or car rentals in Brazil? The data requirements depend on the travel product, search context and rights associated with each source.

Decolar is part of the Despegar travel ecosystem, which has an officially documented B2B API program. However, partner access requires issued credentials and specific permissions. A publicly advertised scraping API is not the same as authorized access to Despegar services.

NenoData works with agreed public, permissioned or otherwise authorized travel sources to organize, validate and deliver structured data. For Decolar-related projects, access rights, field availability and technical feasibility must be confirmed before implementation.

No NenoData-operated Decolar scraper, official API entitlement, existing dataset or live rate feed is pre-confirmed.

Decolar and Despegar: Platform and Market Scope

Decolar is a Brazilian online travel platform associated with the wider Despegar business. Its website serves travelers researching and booking travel products, including accommodation, flights, packages and car rentals.

Decolar's official Brazilian legal information identifies Decolar.com Ltda. The platform operates within the broader Despegar business, which became part of Prosus following the completion of its acquisition on May 15, 2025.

For travel-data research, this relationship matters because Decolar, Despegar and related brands may share parts of a commercial or technical ecosystem without exposing identical offers in every country.

A hotel quote shown for Brazil should not automatically be treated as equivalent to an offer shown on another Despegar market website. Currency, language, locale, travel dates, eligibility and product terms may differ.

For Brazil-focused projects, the initial scope should identify the Decolar website or approved interface, relevant markets and intended use. Corporate affiliation does not establish data equivalence, licensed redistribution rights or API access.

What Travel Data Can Be Evaluated?

Four travel-product categories are relevant to Decolar-related commercial research.

Hotel listings and accommodation rates

Potential information includes property identity, destination, room characteristics, stay dates, occupancy, quoted rates, taxes, fee conditions and availability indicators.

Flight searches and fares

Potential information includes origin and destination airports, dates, airlines, itineraries, stops, fare conditions, baggage inclusions and passenger-specific prices.

Travel packages (pacotes de viagem)

Potential information includes destinations, selected flights and hotels, traveler count, trip duration, package totals, inclusions and cancellation conditions.

Car rentals (aluguel de carros)

Potential information includes pickup and return locations, rental dates, vehicle class, rental duration, quoted amount, mileage conditions and insurance inclusions.

These categories describe potential business requirements, not a verified list of fields accessible through a Decolar scraper or a specific B2B API account.

Despegar's official ecosystem documentation describes hotel and flight interfaces. It separately lists cars and packages among products in development; their presence in the travel business should not be interpreted as confirmation of production-ready API endpoints for every partner.

For broader OTA research, see NenoData's OTA Data Scraping Services.

Potential Decolar Dataset Fields

A reliable travel dataset must describe not only the offer but also the conditions under which it was observed.

The following is a conceptual schema for project scoping. It is not an extract from Decolar, an API response or an existing NenoData dataset.

Potential Decolar-related data structure

Conceptual fields only — not live Decolar data or an API response

Hotel

Property

Stay

Occupancy

Rate

Flight

Route

Travelers

Fare

Baggage

Package

Hotel + Flight

Inclusions

Total

Car rental

Pickup

Return

Class

Terms

↓ Approved source and field availability ↓

Normalize, validate and document provenance

↓

Preserve BRL, dates, locale, pricing context and usage rights

Conceptual schema only — not actual Decolar records or an API response.
Data categoryCandidate fieldsComparison context
HotelProperty ID, property name, city, room type, rate, taxes, amenitiesCheck-in, check-out, guests, rooms
FlightOrigin, destination, carrier, itinerary, fare, baggage, stopsDeparture date, return date, passenger types
PackageDestination, flight components, accommodation, inclusions, package totalTravel dates, duration, traveler count
Car rentalPickup/return location, dates, vehicle category, rental quote, insurance termsRental duration, driver conditions, inclusions
Market contextCountry, locale, currency, applicable promotionBrazilian vs other Latin American markets
Source provenanceSource identifier, observed timestamp, usage rights, validation statusAuditability and permitted reuse

Additional fields can be proposed during scoping, but their availability must be verified against the selected source and the permissions granted.

Keep product schemas separate. A hotel nightly rate, airfare, flight + hotel package total and car rental quote represent different purchases. Combining them into one generic price metric would produce misleading analysis.

The final delivery structure should retain original values, normalized values where needed, missing-field indicators and source attribution.

Decolar API and Authorized Access Options

Is there an official Decolar or Despegar API?

Yes — there is an officially documented Despegar B2B API ecosystem that explicitly references Decolar services. But this is not an open-access public scraping API.

Despegar's official security documentation states that B2B API access requires an API key provided during onboarding. Keys are configured with the permissions applicable to the partner's services, including the relevant HotelDo, Decolar, AfterSales and Activities offerings.

The official ecosystem overview describes hotels, flights, booking flow, after-sales, activities, common assets and other capabilities. This documentation demonstrates a real integration environment but does not establish that every feature, endpoint or dataset is available under every key.

NenoData does not claim to hold Despegar-issued API credentials or an official Decolar partner integration.

Decolar-related access assessment

Conceptual access assessment

Define required data and intended business use

↓

Confirm source rights and API eligibility

Authorized route

Verify key permissions, licensed fields and technical feasibility

↓

Agree project scope

No verified route

Seek authorization or consider approved alternative sources

↓

No assumed extraction

Conceptual access assessment — not evidence of existing Decolar or Despegar API access.

Possible authorized access routes

  1. 1

    Despegar-issued B2B partner credentials

    An eligible organization may be able to pursue the applicable onboarding and commercial agreement with Despegar. The authorized scope depends on the services and permissions attached to its issued credentials. Buyers should confirm whether their intended data retrieval, storage, analytics and redistribution are permitted.

  2. 2

    Direct written permission or commercial data agreement

    A buyer requiring Decolar website content may need a separate written authorization or agreement covering the intended source, collection method and business use. The agreement should establish applicable field categories, volume, frequency, retention and permitted reuse.

  3. 3

    Independently licensed alternative travel data

    An approved airline, hotel, OTA, car rental or travel-data provider may offer records suitable for the buyer's research question. A licensed alternative must preserve its original provenance. It should not be represented as direct Decolar observations unless that origin is independently established.

  4. 4

    Buyer-provided authorized records

    If a business already has access to licensed travel exports, partner records or historical observations, a project may focus on normalization, deduplication, validation and agreed structured delivery. The buyer's processing and redistribution rights still need to be checked.

Official API vs third-party scraping API

AttributeOfficial Despegar B2B APIThird-party Decolar scraping API
Documented byDespegarAn external provider
Access requirementRequires partner-issued API keyUses provider-specific access arrangements
PermissionsAssigned during onboardingSource authorization must be independently checked
FunctionalityService-specific functionalityDepends on the external tool
Commercial useGoverned by applicable agreementTool availability does not establish Decolar's permission

A third-party service returning Decolar-related results is not proof of an official partnership, lawful collection rights or permission to redistribute the data.

Comparing Travel Rates Across Search Contexts

Travel pricing research is meaningful only when the underlying offers are comparable.

Hotel rates

A hotel rate should retain check-in and check-out dates, number of nights, occupancy, room category, rate plan, currency, fee treatment and cancellation conditions. A price per night should not be confused with a full-stay total.

Flight fares

A flight fare requires the route, departure and return dates, number and type of passengers, itinerary, cabin, baggage allowance and applicable fare conditions. Two displayed fares may differ because they include different services.

Vacation packages

A package quote combines multiple travel components. It should include its flights, accommodation, travel dates, traveler count, inclusions and total-price basis. A package total is not an independently observed hotel rate or airfare.

Car rental rates

A rental quote should retain pickup and return times, location, vehicle class, rental duration, driver requirements, mileage, deposit and insurance conditions where available. The cheapest displayed base quote may not represent the same product as an insurance-inclusive offer.

Across categories, the underlying dataset should preserve BRL or other original currency values, market locale, relevant promotions and observation timestamps.

For cross-market comparisons, currency conversion should be documented rather than silently replacing the original value.

See Hotel Pricing Monitoring and Flight Data Scraping Services for related NenoData workflows.

Brazilian Travel Market Research Use Cases

Authorized hotel-rate benchmarking

Hotel revenue teams may want comparable rate observations for defined Brazilian destinations and competitor sets. An authorized dataset can organize property identities, stay dates, room configurations and pricing conditions for analysis, provided suitable sources are available.

Route and flight-fare research

Airline and travel-tech analysts may examine permitted route-level fare information, itinerary options and fare conditions across Brazilian and regional markets. Consistent traveler inputs and observation times help make fare comparisons more meaningful.

Vacation-package market analysis

Travel research teams may study approved package offers by destination, trip length and included travel components. The dataset should preserve bundled pricing and clearly distinguish it from standalone flights or accommodation.

Car-rental comparison

Travel platforms and mobility analysts may compare authorized rental offers by destination, pickup and return period, vehicle category and included conditions. Insurance, deposits and mileage policies should remain identifiable wherever those attributes are within scope.

OTA data feasibility and schema planning

A travel company may need a feasibility assessment before committing to recurring collection. This can clarify which information is essential, which authorized source could provide it, whether a suitable partner API is available and how validated records should be delivered.

How NenoData Would Assess a Decolar Project

NenoData's published travel and OTA services describe agreed-source extraction, standardization, validation and structured delivery. A Decolar-specific engagement would first need to establish authorization and technical feasibility.

  1. 1

    Step 1 — Define the requirement

    Identify the travel products, target Brazilian or Latin American markets, required fields, search inputs, intended commercial use and desired outputs.

  2. 2

    Step 2 — Verify permission and available access

    Review Despegar B2B eligibility, buyer-held credentials where applicable, source agreements or other authorized sources. Confirm the specific services and usage rights available.

  3. 3

    Step 3 — Design and validate the data model

    Establish separate hotel, flight, package and rental schemas as needed. Specify currency handling, date formats, pricing units, source attribution and validation rules.

  4. 4

    Step 4 — Confirm the authorized delivery scope

    If suitable rights and implementation feasibility are established, agree fields, geographic coverage, extraction or integration approach, quality checks, output format and any recurring schedule. If direct access cannot be established, the outcome may instead be a data feasibility plan or an evaluation of licensed alternatives.

NenoData's general travel service pages describe delivery options including CSV, JSON, Excel and API-ready output, with other destinations possible where scoped. These general capabilities do not promise a particular Decolar feed or refresh frequency.

Learn more about How NenoData Works.

What to Include in a Decolar Data Request

A useful enquiry should define the business problem rather than assume that every field can be extracted.

RequirementInformation to provide
Business objectiveHotel benchmarking, airfare analysis, packages, car rentals
ProductsHotels, flights, packages, cars or a defined combination
GeographyBrazil, selected cities, airports or Latin American markets
Source preferenceDecolar website, approved B2B interface or licensed alternative
Access rightsPartner agreement, authorized API permissions or written consent
Travel inputsDates, routes, occupancy, passenger or driver requirements
Required fieldsEssential prices, attributes, conditions and availability
Currency and localeBRL, Portuguese-language market, other locale if required
Intended usageInternal analytics, publication, commercial resale or integration
Historical scopeExisting records, one-time research or future observations
Refresh expectationsOne-time or proposed recurring frequency
DeliveryCSV, Excel, JSON, API-ready records or another scoped destination

Do not send private API secrets through a general enquiry form. Instead, describe the type of authorization or partner access available and arrange an appropriate secure review if the project proceeds.

API, Commercial-Use and Data Limitations

The presence of an official B2B API ecosystem does not mean every Decolar website listing is freely available to commercial data collectors.

  • 1

    Partner credentials are required

    Despegar's documented B2B services require an API key issued through onboarding, with service-specific permissions.

  • 2

    No NenoData platform credentials are confirmed

    This page does not claim that NenoData already holds authorized Decolar or Despegar API access.

  • 3

    No verified production Decolar scraper

    An operational NenoData collection system for Decolar has not been established.

  • 4

    No unrestricted website scraping permission

    The publicly retrievable Decolar terms page did not establish blanket authorization for commercial collection or redistribution. Applicable full terms and agreements require review.

  • 5

    API coverage is not universal

    Official documentation distinguishes supported ecosystem services from products still in development.

  • 6

    No guaranteed fields or rate availability

    Fields, prices and availability depend on the authorized source, market and search context.

  • 7

    No existing dataset claim

    This page does not advertise a ready-made Decolar travel dataset or historical archive.

  • 8

    No assumed cross-market equivalence

    Brazilian Decolar offers cannot automatically be substituted with other Despegar market records.

  • 9

    No guaranteed refresh, coverage or SLA

    Operational conditions must be explicitly confirmed during scoping.

  • 10

    No private customer data collection

    Account credentials, passenger identities, payment details and booking histories are outside this proposed market-research scope.

  • 11

    No implied redistribution rights

    Holding API credentials or possessing an extract does not automatically authorize resale or publication.

Decolar's Privacy Policy, updated July 2026, describes personal information governed by Brazil's LGPD and identifies Decolar.com Ltda. as the controller. This policy is not a commercial scraping license.

The Decolar Terms and Conditions page confirms official operator and channel information, but the retrieved content did not provide enough contractual detail to assert a general commercial scraping permission.

A feasibility review may establish a properly authorized project, identify suitable licensed alternatives or conclude that the proposed collection cannot proceed.

Frequently Asked Questions

Discuss Your Decolar Data Requirements

Need structured travel information for Brazilian hotel benchmarking, airline fare research, vacation-package comparisons or car-rental analysis?

NenoData can review your data objectives, authorized sources, partner API eligibility and proposed dataset structure against its existing travel-data workflow. Share the markets, products, fields and intended use. If your organization already has Despegar B2B permissions or a licensed travel-data source, include that context so the proposed scope can be evaluated accurately.

Authorization, API access, fields, coverage, delivery cadence and commercial use are subject to agreement and project scoping.