How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

WeTravel Leads API

The Leads API from WeTravel — 2 operation(s) for leads.

WeTravel Leads API is one of 17 APIs that WeTravel publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Leads. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an API reference.

This API exposes 2 operations across 2 paths, and defines 6 schemas. It is described by OpenAPI 3.2.0, at version 2.0.0.

Requests are made against 2 base URLs: https://api.wetravel.com/v2, https://api.demo.wetravel.to/v2.

2 operations 2 paths 6 schemas 1 GET1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
2.0.0
Base URL
https://api.wetravel.com/v2
Authentication
HTTP Bearer, API Key
Resource Areas
1

Authentication & Security 2

WeTravel Leads API declares 2 security schemes for authenticating requests. It accepts HTTP bearer tokens (JWT) (bearerAuth). An API key is passed in the header as X-Api-Key (tokenAuth). By default, every request must be authenticated.

Paths & Operations 2

Across 2 paths, the API surfaces 2 operations — 1 GET, 1 POST. Each is listed below with its method, path, parameters, and response codes.

Leads 2
GET
/lead/{id}
Get lead
getLead 1 param → 200
POST
/lead
List Leads
getLeads body → 200

Schemas 6

The contract defines 6 schemas that model the data the API accepts and returns. The most detailed are Trip (19 properties), Lead (11 properties), GetLeads (9 properties), Pagination (6 properties). Each schema is shown below with its type and property counts.

CarbonOffset
object
Carbon Offset Contribution
3 properties 3 required
Trip
object
Trip model
19 properties 12 required
Pagination
object
Pagination object
6 properties
Question
object
Question object
2 properties
Lead
object
Lead object
11 properties
GetLeads
object
Get leads
9 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

wetravel-leads-api-openapi.yml Raw ↑

Other APIs WeTravel publishes across the network.

WeTravel Access token API
WeTravel Add-ons API
WeTravel Discounts API
WeTravel Images API
WeTravel Included items API
WeTravel Not Included items API
WeTravel Orders API
WeTravel Packages API
WeTravel Paragraphs API
WeTravel Participant Information API
WeTravel Payment Links API
WeTravel Payment Plans API
Where this information came from

This is an independent, third-party profile of WeTravel Leads API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.