Despegar Discovery API
The Discovery API from Despegar — 1 operation(s) for discovery.
Work with this as data
Every API here is available over the APIs.io API and to AI agents over MCP.
MCP server
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
Tools for apis
7 MCP tools reach this
find_apisBrowse and filter every API in the catalog.get_api_artifactsOne API's artifacts, grouped by type.get_openapiThe primary OpenAPI for this API.find_similar_apisAPIs that look like this one.apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.resolveTurn a domain, URL or GitHub org into the provider it belongs to.find_cohortsEvery scored population of providers in the catalog.
Call it yourself
curl for this page
This API
curl "https://apis.io/api/v1/apis/despegar-discovery-api"
All apis
curl "https://apis.io/api/v1/apis?limit=25"Discovery needs no key. Ratings and market analysis are Pro.
Get an API key
Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.
A second provider on the same verified email joins the account you already have.
OpenAPI Specification
openapi: 3.2.0
info:
title: Activities Availability Discovery API
version: 1.0.0
description: 'API for activities: tickets, modalities, availability, prebook, payments, and booking. Authentication via API Key.'
servers:
- url: https://api-dev.despegar.com/v3/activities-api
description: Sandbox
- url: https://apis-uat.despegar.com/v3/activities-api
description: UAT
- url: https://api.despegar.com/v3/activities-api
description: Production
security:
- ApiKeyAuth: []
tags:
- name: Discovery
paths:
/discovery:
get:
tags:
- Discovery
summary: Discovery
parameters:
- name: site
in: query
required: true
schema:
type: string
description: Refers to the country code
example: br
- name: destination
in: query
required: true
schema:
type: string
description: This field must be populated with the IATA code corresponding to each destination.
example: SAO
- name: language
in: query
required: true
schema:
type: string
example: pt
responses:
'200':
description: Successful response
content:
application/json:
schema:
type: array
items:
type: object
properties:
items:
type: array
items:
type: object
properties:
tracking_id:
type: string
type:
type: string
enum:
- TOUR
- TICKET
name:
type: string
'400':
description: Invalid request
content:
application/json:
schema:
type: object
'401':
description: Unauthorized
content:
application/json:
schema:
type: object
'403':
description: FORBIDDEN
content:
application/json:
schema:
type: object
'404':
description: Not found
content:
application/json:
schema:
type: object
'500':
description: Internal server error
content:
application/json:
schema:
type: object
components:
securitySchemes:
ApiKeyAuth:
type: apiKey
in: header
name: x-apikey
BearerAuth:
type: http
scheme: bearer
x-readme: {}