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.

WeTravel publishes 17 API contracts indexed on the APIs.io network, including Access token API, Add-ons API, Discounts API, and 14 more. Tagged areas include Company, Business Applications, Travel, Booking, and Payments.

The WeTravel catalog on APIs.io includes 1 event-driven AsyncAPI specification and 1 Spectral governance ruleset.

WeTravel’s developer surface includes documentation, API reference, getting-started guide, support, changelog, authentication, sandbox, and 23 more developer resources.

🌐 Visit website 📡 Profile data on GitHub

56.9/100 strong ▬ flat Agent 37/100 agent ready Heartbeat 26/100 dormant Full breakdown ↓
scored 2026-11-06 · rubric v0.27.0 · Show this score on your site →

AccessFreemiumSelf serve⚡ Free to try

1 published contract 1 MCP Servers 3 Agent Skills

Company Business Applications Travel Booking PaymentsTrip ManagementTour OperatorsTravel Technology

What this lets a business do 3

Business capabilities this provider's published APIs can perform, derived from its own contracts. Browse all capabilities →

Travel Product & Inventory Management

BC-4000

Add-onsImagesPackagesParagraphsTrips

POST /draft_trips/{trip_uuid}/options POST /draft_trips/{trip_uuid}/images POST /draft_trips/{trip_uuid}/packages POST /draft_trips

Reservation & Booking Management

BC-4020

OrdersTransactions

PUT /bookings/orders/{order_id}/edit_payment_plan GET /bookings/trips/{trip_uuid}/orders/{order_id} GET /transactions/{uuid}

Travel Revenue & Yield Management

BC-4030

Discounts

POST /draft_trips/{trip_uuid}/discounts

Kin Score

Kin Score How this is scored →
scored 2026-11-06 · rubric v0.27.0

Composite quality — 56.9/100 · strong

Contract Quality 11.7 / 19

Developer Ergonomics 9.0 / 15

Access Clarity 5.9 / 15

Operational Transparency 7.6 / 10

Contract Governance 1.6 / 9

Discoverability 5.6 / 8

Regulatory Posture 3.1 / 15

Create-or-Update Ergonomics 2.2 / 10

Agent readiness — 37/100 · agent ready

Machine-Readable Contract 18 / 18

Agentic Access Contract 10 / 10

Documented Reversibility 0 / 6

MCP Server 12 / 12

Machine-Readable Auth 10 / 10

Idempotency 0 / 9

Stable Error Semantics 8 / 8

Request/Response Examples 7 / 7

Rate-Limit Signaling 7 / 7

Typed Event Surface 6 / 6

Agent Skills 5 / 5

Well-Known Catalog 0 / 4

Consent & Bot Identity 0 / 3

A2A Agent Card 0 / 8

Dry-Run / Simulate Mode 0 / 4

Delegated User Identity 0 / 6

Protected Resource Metadata 0 / 5

Registration Without a Human 0 / 6

Agentic Commerce Well-Known Document 0 / 5

Pagination 0 / 5

Distinct Operations 3 / 3

MCP Tool Quality 6 / 6

Regulatory Posture applies to this provider. Its tags matched the Payments regime, so Regulatory Posture carries 15 points of the composite. If this regime is wrong for your business, say so on your provider repo — the applicability map is public and we will correct it.

Create-or-Update Ergonomics applies to this provider. This API accepts writes, so it carries 10 points of the composite. It is scored from the published contracts themselves: whether a caller can create-or-update in one call, whether the write accepts a key the caller already holds, and whether the response says which branch ran. Without that, every write needs a search-and-branch in front of it, and the first time that check is skipped a duplicate record is created. Scored against the observed mean rather than raw — a provider at the catalog average is unchanged by this facet, not penalised by it.

The six quality facets above are damped to 75 points between them, because the conditional facet above carries the other 25. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 75% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.

Show this score on your site.

It updates itself when the score changes. Paste this where you link to your API docs:

<a href="https://apis.io/providers/wetravel/"><img src="https://apis.io/badge/wetravel/card.svg" alt="WeTravel on APIs.io — Kin Score by API Evangelist"></a>

Other styles, a README pill and a shields.io endpoint are on the badge page.

Raise your score.

Agent readiness — checks not met, largest first (exact, from this profile):

Idempotency +9 pts — OpenAPI mutating operations declare an idempotency key — a header, a request-body property, or a named de-duplication token whose own description says so (verified); else common[].type matches /idempoten/i (documented)
A2A Agent Card +8 pts — a2a/-a2a.yml manifest, graded on conformance.grade against A2A 1.0.0
Registration Without a Human +6 pts — a `registration_endpoint` in the served RFC 8414 / OIDC discovery document
Delegated User Identity +6 pts — a served discovery document listing authorization_code in grant_types_supported (served), else an oauth2 authorizationCode flow or openIdConnect declared in an OpenAPI (documented)
Documented Reversibility +6 pts — a reversal operation in the contract, graded up when a window is documented too
Pagination +5 pts — share of collection GETs (an array, or one wrapped in data/items/results ...) that declare a page/limit/offset/cursor parameter, a Link header or a next/cursor field; na with no collection GETs

5 more unmet checks in the Agent Readiness table above.

Kin Score — facets with the most composite points still available (weight × headroom):

Access Clarity scores 39.5 — up to +12.1 composite points
Contract Governance scores 18.2 — up to +9.8 composite points
Contract Quality scores 62.2 — up to +9.5 composite points

Each check links to what satisfies it. Publish the artifact, or tell us where it already lives, and the score moves on the next scoring run.

Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from the provider profile at artifacts.apis.io/wetravel/apis.yml: open an issue on github.com/api-evangelist/wetravel to ask a question or point us at an artifact you publish. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

Markets this provider is in provisional

The Kin Score Market layer reads a provider inside its market: its position, and how deep its integrations go. Depth is only comparable within a position. Provisional and unweighted: not part of the Kin Score or agent readiness.

Market	Position	Depth	Registered MCP server	Declares compatibility
Stripe App Marketplace and Partner Ecosystem (builders on Stripe)	standard	43.4	-	-
OCTO Tours, Activities & Attractions Connectivity (members, known implementations, self-certification)	standard	43.4	-	-

Registered MCP server and declares compatibility are report only — not weighted. Undeclared means we found nothing we can read, so there is no number: we never infer integrations.

Standards implemented 2

Standards this provider implements or carries. De facto ones are profiled and measured by the API Commons; formal ones come from the standards directory and are linked by the provider's own tags. The evidence column says how each claim was established — not that it was made.

Model Context Protocol (MCP)

measured — observed by APIs.io (verified)

OpenAPI

measured — observed by APIs.io (published)

APIs 17

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 for all 17

Open Collections 17

Open, tool-agnostic API collections (OpenAPI-derived and Bruno).

WeTravel Partner Access token API

OPEN COLLECTION

WeTravel Partner Access token Add-ons API

OPEN COLLECTION

WeTravel Partner Access token Discounts API

OPEN COLLECTION

WeTravel Partner Access token Images API

OPEN COLLECTION

WeTravel Partner Access token Included items API

OPEN COLLECTION

WeTravel Partner Access token Leads API

OPEN COLLECTION

WeTravel Partner Access token Not Included items API

OPEN COLLECTION

WeTravel Partner Access token Orders API

OPEN COLLECTION

WeTravel Partner Access token Packages API

OPEN COLLECTION

WeTravel Partner Access token Paragraphs API

OPEN COLLECTION

WeTravel Partner Access token Participant Information API

OPEN COLLECTION

WeTravel Partner Access token Payment Links API

OPEN COLLECTION

WeTravel Partner Access token Payment Plans API

OPEN COLLECTION

WeTravel Partner Access token Suppliers API

OPEN COLLECTION

WeTravel Partner Access token Transactions API

OPEN COLLECTION

WeTravel Partner Access token Trip Overview API

OPEN COLLECTION

WeTravel Partner Access token Trips API

OPEN COLLECTION

Scroll for all 17

MCP Servers 1

Model Context Protocol servers that expose these APIs to AI agents.

WeTravel MCP Server

Remote MCP server at developer.wetravel.com over HTTP; 7 tools listed.

MCP SERVER

Agent Skills 3

Packaged agent skills for driving this provider's APIs from an AI assistant.

Create and publish a WeTravel trip

AGENT SKILL

Create and publish a WeTravel payment link

AGENT SKILL

Sync WeTravel bookings and transactions

AGENT SKILL

WeTravel API pricing

Prices published by WeTravel, read 2026-10-28 from product.wetravel.com/pricing.

Plan	Price
Basic	$0 0/month/month Includes: Essential payment and trip management tools
Pro	$79 79/month/month per organization, unlimited team members Includes: Advanced features: custom branding, unlimited itineraries, eSignatures, Auto-Billing, inventory, Par
Enterprise	Book a Demo Includes: Custom enterprise solution

Plan details, limits and sources →

Billed by: organization · FinOps profile →

Pricing Plans 2

Published pricing tiers and plan structures.

Wetravel Plans Pricing

3 plans

PLANS

Wetravel Price Estimates

0 plans

PLANS

Rate Limits 1

Documented rate limits and quota policies.

Wetravel Rate Limits

1 limits

RATE LIMITS

Service Levels 1

Uptime the provider promises or reports, as SLA4OAI. Read from its own pages; APIs.io runs no monitors.

WeTravel

SLA

FinOps 1

Cost, billing, and metering signals for API financial operations.

Wetravel Finops

FINOPS

Event Specifications 1

AsyncAPI definitions for this provider's event-driven and streaming APIs.

Wetravel Webhooks

ASYNCAPI

Spectral Rules 1

Spectral governance rulesets for linting and validating these APIs.

WeTravel API Rules

59 rules · 43 errors 13 warnings 3 info

SPECTRAL

OpenAPI Overlays 1

Overlays applied on top of this provider's contracts. Each card says who wrote it: a document the provider publishes, or one API Evangelist derived or generated.

Wetravel Partner Overlay

2 actions · update · wetravel-partner-openapi.json

DERIVED

Security Posture 3

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Wetravel Authentication

apiKey/http · 2 schemes

SECURITY

Wetravel Domain Security

TLSv1.3 · HSTS · DNSSEC · DMARC

SECURITY

Wetravel Vulnerability Disclosure

no policy recorded

SECURITY

Agentic Access 1

Recommended x-agentic-access execution contracts for AI agents.

Wetravel Agentic Access

77 operations · 44 acting

AGENTIC

Resources

Get Started 3

Portal, sign-up, and the first successful call

DeveloperPortal

DeveloperPortal

GettingStarted

GettingStarted

Sandbox

Sandbox

Documentation 2

Reference material describing how the API behaves

Documentation

Documentation

APIReference

APIReference

Agent Surfaces 4

MCP servers, agent skills, and machine-readable catalogs

MCPServer

AgentSkill

AgenticAccess

LLMsTxt

Design & Contract 6

Pagination, idempotency, versioning, errors, and events

Lifecycle

Conventions

ErrorCatalog

DataModel

Conformance

Webhooks

Build 1

SDKs, sample code, and the tooling you integrate with

GitHubOrganization

GitHubOrganization

Access & Security 4

Authentication, authorization, and security posture

Authentication

Authentication

Security

Security

VulnerabilityDisclosure

VulnerabilityDisclosure

DomainSecurity

DomainSecurity

Operate 5

Status, limits, changes, and where to get help

Support

StatusPage

ChangeLog

Deprecation

RateLimits

Commercial 1

Pricing, plans, and the legal terms of use

Plans

Plans

Company 2

The organization behind the API

BlogRSS

BlogRSS

Website

Website

Other 2

Properties that don't map to a standard resource type

CapabilityMap

CapabilityMap

Overlay

Overlay

Source (apis.yml)

aid: wetravel
deliveryModel:
  model: unknown
  open_source: false
  commercial: false
  callable_host: true
  label: Delivery model not determined — needs a product licence on record
  confidence: low
  source:
  - openapi
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: freemium
  onboarding: self-serve
  trial: false
  try_now: true
  public: false
  gated: none
  gated_source:
  - onboarding
  label: Freemium · Self-serve signup
  confidence: high
  source:
  - plans
  - authentication
  - rate-limits
  - security
  - sandbox
  generated: '2026-11-06'
  method: derived
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/icons/wetravel.png
name: WeTravel
description: 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.
url: https://raw.githubusercontent.com/api-evangelist/wetravel/refs/heads/main/apis.yml
x-type: company
x-source: vc-portfolio
x-backed-by:
- index-ventures
- sapphire-ventures
x-tier: profiled
x-tier-reason: enriched-from-developer-hub
specificationVersion: '0.23'
created: '2026-07-17'
modified: '2026-10-06'
x-docs-platform: readme
x-docs-platform-confidence: high
x-docs-platform-checked: 2026-10-17
tags:
- Company
- Business Applications
- Travel
- Booking
- Payments
- Trip Management
- Tour Operators
- Travel Technology
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
apis:
- aid: wetravel:wetravel-access-token-api
  name: WeTravel Access token API
  description: The Access token API from WeTravel — 1 operation(s) for access token.
  humanURL: https://developer.wetravel.com/
  baseURL: https://api.wetravel.com/v2
  tags:
  - Access Token
  tags_raw:
  - Access token
  properties:
  - type: OpenAPI
    url: openapi/wetravel-access-token-api-openapi.yml
  - type: Documentation
    url: https://developer.wetravel.com/docs/getting-started
  - type: APIReference
    url: https://developer.wetravel.com/reference
- aid: wetravel:wetravel-add-ons-api
  name: WeTravel Add-ons API
  description: The Add-ons API from WeTravel — 2 operation(s) for add-ons.
  humanURL: https://developer.wetravel.com/
  baseURL: https://api.wetravel.com/v2
  tags:
  - Addons
  tags_raw:
  - Add-ons
  properties:
  - type: OpenAPI
    url: openapi/wetravel-add-ons-api-openapi.yml
  - type: Documentation
    url: https://developer.wetravel.com/docs/getting-started
  - type: APIReference
    url: https://developer.wetravel.com/reference
- aid: wetravel:wetravel-discounts-api
  name: WeTravel Discounts API
  description: The Discounts API from WeTravel — 2 operation(s) for discounts.
  humanURL: https://developer.wetravel.com/
  baseURL: https://api.wetravel.com/v2
  tags:
  - Discounts
  properties:
  - type: OpenAPI
    url: openapi/wetravel-discounts-api-openapi.yml
  - type: Documentation
    url: https://developer.wetravel.com/docs/getting-started
  - type: APIReference
    url: https://developer.wetravel.com/reference
- aid: wetravel:wetravel-images-api
  name: WeTravel Images API
  description: The Images API from WeTravel — 2 operation(s) for images.
  humanURL: https://developer.wetravel.com/
  baseURL: https://api.wetravel.com/v2
  tags:
  - Image
  tags_raw:
  - Images
  properties:
  - type: OpenAPI
    url: openapi/wetravel-images-api-openapi.yml
  - type: Documentation
    url: https://developer.wetravel.com/docs/getting-started
  - type: APIReference
    url: https://developer.wetravel.com/reference
- aid: wetravel:wetravel-included-items-api
  name: WeTravel Included items API
  description: The Included items API from WeTravel — 2 operation(s) for included items.
  humanURL: https://developer.wetravel.com/
  baseURL: https://api.wetravel.com/v2
  tags:
  - Included items
  properties:
  - type: OpenAPI
    url: openapi/wetravel-included-items-api-openapi.yml
  - type: Documentation
    url: https://developer.wetravel.com/docs/getting-started
  - type: APIReference
    url: https://developer.wetravel.com/reference
- aid: wetravel:wetravel-leads-api
  name: WeTravel Leads API
  description: The Leads API from WeTravel — 2 operation(s) for leads.
  humanURL: https://developer.wetravel.com/
  baseURL: https://api.wetravel.com/v2
  tags:
  - Leads
  properties:
  - type: OpenAPI
    url: openapi/wetravel-leads-api-openapi.yml
  - type: Documentation
    url: https://developer.wetravel.com/docs/getting-started
  - type: APIReference
    url: https://developer.wetravel.com/reference
- aid: wetravel:wetravel-not-included-items-api
  name: WeTravel Not Included items API
  description: The Not Included items API from WeTravel — 2 operation(s) for not included items.
  humanURL: https://developer.wetravel.com/
  baseURL: https://api.wetravel.com/v2
  tags:
  - Not Included items
  properties:
  - type: OpenAPI
    url: openapi/wetravel-not-included-items-api-openapi.yml
  - type: Documentation
    url: https://developer.wetravel.com/docs/getting-started
  - type: APIReference
    url: https://developer.wetravel.com/reference
- aid: wetravel:wetravel-orders-api
  name: WeTravel Orders API
  description: The Orders API from WeTravel — 7 operation(s) for orders.
  humanURL: https://developer.wetravel.com/
  baseURL: https://api.wetravel.com/v2
  tags:
  - Order
  tags_raw:
  - Orders
  properties:
  - type: OpenAPI
    url: openapi/wetravel-orders-api-openapi.yml
  - type: Documentation
    url: https://developer.wetravel.com/docs/getting-started
  - type: APIReference
    url: https://developer.wetravel.com/reference
- aid: wetravel:wetravel-packages-api
  name: WeTravel Packages API
  description: The Packages API from WeTravel — 2 operation(s) for packages.
  humanURL: https://developer.wetravel.com/
  baseURL: https://api.wetravel.com/v2
  tags:
  - Packages
  properties:
  - type: OpenAPI
    url: openapi/wetravel-packages-api-openapi.yml
  - type: Documentation
    url: https://developer.wetravel.com/docs/getting-started
  - type: APIReference
    url: https://developer.wetravel.com/reference
- aid: wetravel:wetravel-paragraphs-api
  name: WeTravel Paragraphs API
  description: The Paragraphs API from WeTravel — 2 operation(s) for paragraphs.
  humanURL: https://developer.wetravel.com/
  baseURL: https://api.wetravel.com/v2
  tags:
  - Paragraphs
  properties:
  - type: OpenAPI
    url: openapi/wetravel-paragraphs-api-openapi.yml
  - type: Documentation
    url: https://developer.wetravel.com/docs/getting-started
  - type: APIReference
    url: https://developer.wetravel.com/reference
- aid: wetravel:wetravel-participant-information-api
  name: WeTravel Participant Information API
  description: The Participant Information API from WeTravel — 2 operation(s) for participant information.
  humanURL: https://developer.wetravel.com/
  baseURL: https://api.wetravel.com/v2
  tags:
  - Participant Information
  properties:
  - type: OpenAPI
    url: openapi/wetravel-participant-information-api-openapi.yml
  - type: Documentation
    url: https://developer.wetravel.com/docs/getting-started
  - type: APIReference
    url: https://developer.wetravel.com/reference
- aid: wetravel:wetravel-payment-links-api
  name: WeTravel Payment Links API
  description: The Payment Links API from WeTravel — 3 operation(s) for payment links.
  humanURL: https://developer.wetravel.com/
  baseURL: https://api.wetravel.com/v2
  tags:
  - Payment Links
  properties:
  - type: OpenAPI
    url: openapi/wetravel-payment-links-api-openapi.yml
  - type: Documentation
    url: https://developer.wetravel.com/docs/getting-started
  - type: APIReference
    url: https://developer.wetravel.com/reference
- aid: wetravel:wetravel-payment-plans-api
  name: WeTravel Payment Plans API
  description: The Payment Plans API from WeTravel — 2 operation(s) for payment plans.
  humanURL: https://developer.wetravel.com/
  baseURL: https://api.wetravel.com/v2
  tags:
  - Payment Plans
  properties:
  - type: OpenAPI
    url: openapi/wetravel-payment-plans-api-openapi.yml
  - type: Documentation
    url: https://developer.wetravel.com/docs/getting-started
  - type: APIReference
    url: https://developer.wetravel.com/reference
- aid: wetravel:wetravel-suppliers-api
  name: WeTravel Suppliers API
  description: The Suppliers API from WeTravel — 2 operation(s) for suppliers.
  humanURL: https://developer.wetravel.com/
  baseURL: https://api.wetravel.com/v2
  tags:
  - Suppliers
  properties:
  - type: OpenAPI
    url: openapi/wetravel-suppliers-api-openapi.yml
  - type: Documentation
    url: https://developer.wetravel.com/docs/getting-started
  - type: APIReference
    url: https://developer.wetravel.com/reference
- aid: wetravel:wetravel-transactions-api
  name: WeTravel Transactions API
  description: The Transactions API from WeTravel — 2 operation(s) for transactions.
  humanURL: https://developer.wetravel.com/
  baseURL: https://api.wetravel.com/v2
  tags:
  - Transaction
  tags_raw:
  - Transactions
  properties:
  - type: OpenAPI
    url: openapi/wetravel-transactions-api-openapi.yml
  - type: Documentation
    url: https://developer.wetravel.com/docs/getting-started
  - type: APIReference
    url: https://developer.wetravel.com/reference
- aid: wetravel:wetravel-trip-overview-api
  name: WeTravel Trip Overview API
  description: The Trip Overview API from WeTravel — 2 operation(s) for trip overview.
  humanURL: https://developer.wetravel.com/
  baseURL: https://api.wetravel.com/v2
  tags:
  - Trip Overview
  properties:
  - type: OpenAPI
    url: openapi/wetravel-trip-overview-api-openapi.yml
  - type: Documentation
    url: https://developer.wetravel.com/docs/getting-started
  - type: APIReference
    url: https://developer.wetravel.com/reference
- aid: wetravel:wetravel-trips-api
  name: WeTravel Trips API
  description: The Trips API from WeTravel — 3 operation(s) for trips.
  humanURL: https://developer.wetravel.com/
  baseURL: https://api.wetravel.com/v2
  tags:
  - Trips
  properties:
  - type: OpenAPI
    url: openapi/wetravel-trips-api-openapi.yml
  - type: Documentation
    url: https://developer.wetravel.com/docs/getting-started
  - type: APIReference
    url: https://developer.wetravel.com/reference
common:
- type: Plans
  url: plans/wetravel-plans-pricing.yml
- url: https://academy.wetravel.com/rss.xml
  type: BlogRSS
- type: CapabilityMap
  url: capabilities/wetravel-capability-edges.yml
  name: WeTravel Business Capability Map
- type: Overlay
  url: overlays/wetravel-partner-overlay.yaml
- type: DeveloperPortal
  url: https://developer.wetravel.com/
- type: Documentation
  url: https://developer.wetravel.com/docs/getting-started
- type: APIReference
  url: https://developer.wetravel.com/reference
- type: GettingStarted
  url: https://developer.wetravel.com/docs/getting-started
- type: Support
  url: https://help.wetravel.com/en/
- type: StatusPage
  url: https://status.wetravel.com/
- type: GitHubOrganization
  url: https://github.com/wetravel-com
- type: ChangeLog
  url: changelog/wetravel-changelog.yml
- type: Deprecation
  url: https://developer.wetravel.com/reference/migration-v2-to-v3
- type: Lifecycle
  url: lifecycle/wetravel-lifecycle.yml
- type: Authentication
  url: authentication/wetravel-authentication.yml
- type: Conventions
  url: conventions/wetravel-conventions.yml
- type: ErrorCatalog
  url: errors/wetravel-problem-types.yml
- type: DataModel
  url: data-model/wetravel-data-model.yml
- type: Conformance
  url: conformance/wetravel-conformance.yml
- type: RateLimits
  url: rate-limits/wetravel-rate-limits.yml
- type: Webhooks
  url: asyncapi/wetravel-webhooks.yml
- type: MCPServer
  url: mcp/wetravel-mcp.yml
- type: AgentSkill
  url: skills/_index.yml
- type: AgenticAccess
  url: agentic-access/wetravel-agentic-access.yml
- type: LLMsTxt
  url: llms/wetravel-llms.txt
- type: Sandbox
  url: sandbox/wetravel-sandbox.yml
- type: Security
  url: https://www.wetravel.com/disclosure
- type: VulnerabilityDisclosure
  url: security/wetravel-vulnerability-disclosure.yml
- type: DomainSecurity
  url: security/wetravel-domain-security.yml
- type: Website
  url: https://www.wetravel.com/
x-enrichment:
  date: '2026-07-21'
  status: enriched
  artifacts_added: 19
  pass: local-v1

WeTravel API — frequently asked questions

Does WeTravel have an API?

Yes. APIs.io lists 17 APIs from WeTravel, including WeTravel Access token API, WeTravel Add-ons API and WeTravel Discounts API, and 14 more.

Is there an OpenAPI specification for the WeTravel API?

Yes. APIs.io indexes 17 OpenAPI specifications for WeTravel, each linked for download from this page.

How do I authenticate with the WeTravel API?

WeTravel uses bearer-token authentication (apiKey/http · 2 schemes). The details are profiled on APIs.io as Wetravel Authentication.

How much does the WeTravel API cost?

WeTravel publishes its prices; its Basic plan is $0 0/month/month as of 2026-10-28. APIs.io lists 3 pricing plans for WeTravel, with each plan's price, limits and inclusions under Pricing on this page.

Does WeTravel have an MCP server?

Yes. APIs.io lists 1 MCP server for WeTravel: Remote MCP server at developer.wetravel.com over HTTP; 7 tools listed.

Is the WeTravel API ready for AI agents?

WeTravel has a Kin Score of 56.9 out of 100 (strong) and an Agent Readiness score of 36.9 (agent-ready), scored by API Evangelist on 2026-11-06.

Work with this as data

Every provider 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 providers

9 MCP tools reach this

find_providersBrowse and filter every provider in the catalog.
get_provider_artifactsEvery artifact this provider publishes, grouped by type.
get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
get_provider_ratingPRO — composite, band, trend and facet scores.
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.

All 92 tools →

Call it yourself

curl for this page

This provider

curl "https://apis.io/api/v1/providers/wetravel"

All providers

curl "https://apis.io/api/v1/providers?limit=25"

Every operation they expose

curl "https://apis.io/api/v1/providers/wetravel/operations?limit=25"

How their score was established

curl "https://apis.io/api/v1/providers/wetravel/evidence"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

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.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.