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 Orders API

The Orders API from WeTravel — 7 operation(s) for orders.

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

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

This API exposes 7 operations across 7 paths, and defines 12 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.

7 operations 7 paths 12 schemas 3 GET4 PUT

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 Orders 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 7

Across 7 paths, the API surfaces 7 operations — 3 GET, 4 PUT. Each is listed below with its method, path, parameters, and response codes.

Orders 7
PUT
/bookings/orders/{order_id}/edit_payment_plan
Edit payment plan for an order
editPaymentPlanByOrderId 1 param body → 200
PUT
/bookings/orders/batch/edit_payment_plan
Edit payment plans for multiple orders
editPaymentPlanByOrderIds body → 200
GET
/bookings/trips/{trip_uuid}/orders/{order_id}
Get an order
getOrderById 2 params → 200
GET
/bookings/trips/{trip_uuid}/bookings
List orders
getOrders 2 params → 200
GET
/bookings/trips/{trip_uuid}/bookings/{buyer_id}
List a buyer's orders
getOrdersByBuyer 3 params → 200
PUT
/bookings/orders/{order_id}/set_custom_price
Set a custom price for an order
setCustomPriceByOrderId 1 param body → 200
PUT
/bookings/orders/batch/set_custom_price
Set custom prices for multiple orders
setCustomPriceByOrderIds body → 200

Schemas 12

The contract defines 12 schemas that model the data the API accepts and returns. The most detailed are Order (34 properties), OrderSummary (22 properties), Option (9 properties), Donation (6 properties). Each schema is shown below with its type and property counts.

Option
object
Add-on model
9 properties 3 required
Donation
object
Donation object
6 properties
Buyer
object
Buyer object
3 properties
OrderSummary
object
OrderSummary object
22 properties
Pagination
object
Pagination object
6 properties
CustomPrice
object
3 properties 2 required
BatchCustomPrice
object
4 properties 3 required
Order
object
Order object
34 properties
EsignDocumentSummary
object
EsignDocument object
2 properties
PaymentPlan
object
PaymentPlan model
4 properties
SnowflakeId
string
64-bit Snowflake identifier encoded as a decimal string
Installment
object
2 properties 2 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

wetravel-orders-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 Leads API
WeTravel Not Included items 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 Orders 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.