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

The Packages API from WeTravel — 2 operation(s) for packages.

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

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

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

5 operations 2 paths 3 schemas 1 DELETE2 GET1 PATCH1 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 Packages 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 5

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

Packages 5
POST
/draft_trips/{trip_uuid}/packages
Create package
createPackage 1 param body → 201
GET
/draft_trips/{trip_uuid}/packages
List packages
getPackages 1 param → 200
DELETE
/draft_trips/{trip_uuid}/packages/{id}
Delete package
deletePackage 2 params → 204
GET
/draft_trips/{trip_uuid}/packages/{id}
Get package
getPackageById 2 params → 200
PATCH
/draft_trips/{trip_uuid}/packages/{id}
Update package
updatePackage 2 params body → 200

Schemas 3

The contract defines 3 schemas that model the data the API accepts and returns. The most detailed are Package (9 properties), UpdatePackage (7 properties), CreatePackage (7 properties). Each schema is shown below with its type and property counts.

Package
object
Package model
9 properties 4 required
CreatePackage
object
Create Package
7 properties 2 required
UpdatePackage
object
Update Package
7 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

wetravel-packages-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 Orders 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 Packages 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.