WeTravel
WeTravel is a booking and payments platform for the multi-day and group travel industry - tour operators, retreat and adventure-travel organizers, and travel agencies. Its Partner API (Trip Builder, Bookings, Payments/Payment Links, Transactions, Suppliers and Leads) lets travel companies programmatically create WeTravel trip and booking pages from their own IT systems and sync customer, order, payment and transaction data, while WeTravel handles the customer-facing booking experience, automated payment plans and low-cost payment processing. A Zapier integration extends the same data to 8000+ services, and a documented webhook catalog streams booking, payment, transaction, trip and lead events. Backed by Index Ventures and Sapphire Ventures.
Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.
API Evangelist profiles WeTravel the way a machine reads it — 24 machine-readable artifacts across 17 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — WeTravel scores 49.2/100 (developing), with a separate agent-readiness read of 78/100 (agent native). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile WeTravel
Each block below is one kind of artifact we hold for WeTravel. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 17
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
WeTravel Access token API
The Access token API from WeTravel — 1 operation(s) for access token.
WeTravel Add-ons API
The Add-ons API from WeTravel — 2 operation(s) for add-ons.
WeTravel Discounts API
The Discounts API from WeTravel — 2 operation(s) for discounts.
WeTravel Images API
The Images API from WeTravel — 2 operation(s) for images.
WeTravel Included items API
The Included items API from WeTravel — 2 operation(s) for included items.
WeTravel Leads API
The Leads API from WeTravel — 2 operation(s) for leads.
WeTravel Not Included items API
The Not Included items API from WeTravel — 2 operation(s) for not included items.
WeTravel Orders API
The Orders API from WeTravel — 7 operation(s) for orders.
WeTravel Packages API
The Packages API from WeTravel — 2 operation(s) for packages.
WeTravel Paragraphs API
The Paragraphs API from WeTravel — 2 operation(s) for paragraphs.
WeTravel Participant Information API
The Participant Information API from WeTravel — 2 operation(s) for participant information.
WeTravel Payment Links API
The Payment Links API from WeTravel — 3 operation(s) for payment links.
WeTravel Payment Plans API
The Payment Plans API from WeTravel — 2 operation(s) for payment plans.
WeTravel Suppliers API
The Suppliers API from WeTravel — 2 operation(s) for suppliers.
WeTravel Transactions API
The Transactions API from WeTravel — 2 operation(s) for transactions.
WeTravel Trip Overview API
The Trip Overview API from WeTravel — 2 operation(s) for trip overview.
WeTravel Trips API
The Trips API from WeTravel — 3 operation(s) for trips.
Scroll within the panel for all 17 ·
MCP Servers 1
Model Context Protocol servers expose these APIs directly to AI agents. We profile them because agent-native access is the fastest-growing way this provider's capabilities actually get used.
Model Context Protocol servers that expose these APIs to AI agents.
wetravel-mcp.yml
MCP SERVERRate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Wetravel Rate Limits
RATE LIMITSEvent Specifications 1
Not every API is request/response. AsyncAPI describes the event-driven and streaming side — the webhooks and channels — so the asynchronous half of the interface is documented the same way the synchronous half is.
AsyncAPI definitions for this provider's event-driven and streaming APIs.
Wetravel Webhooks
ASYNCAPISecurity Posture 3
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for WeTravel — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 3
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 4
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 6
Pagination, idempotency, versioning, errors, and events
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 4
Authentication, authorization, and security posture
Operate 5
Status, limits, changes, and where to get help
Company 1
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/wetravel · machine-readable index on apis.io