API Reference

Create a trip

post
https://api.wetravel.com/v3/trips

Create a new trip and publish it immediately. A trip defines the core booking configuration, including dates, capacity, pricing structure, and participant settings.

Recent Requests
Log in to see full request history
TimeStatusUser Agent
Retrieving recent requests…
LoadingLoading…
Body Params

Trip creation request model.

string
required
length ≤ 255

Title of the trip

string
required
length ≤ 60000

Description of the trip. In v2, publishing required a first paragraph; in v3, this requirement is replaced by the description field.

string
length ≤ 255

Optional trip reference set by you. Not visible to participants; only visible in your WeTravel dashboard and reporting. In v2, this field was named trip_id.

string

User ID of the team member account you want to assign ownership to.

string
required
length between 3 and 3
Defaults to USD

Currency code for the trip (ISO 4217). Defaults to USD when not provided.

date

Trip start date (ISO 8601 YYYY-MM-DD). Required when recurring is false.

date

Trip end date (ISO 8601 YYYY-MM-DD). Required when recurring is false.

int32
≥ 1

Trip duration in days. Required when recurring is true.

int32
required
1 to 9999
Defaults to 1

Minimum number of participants required

int32
required
1 to 9999
Defaults to 25

Maximum number of participants allowed

string
enum
required

Controls whether the trip is publicly accessible or only visible to the organizer.

Allowed:
string
enum

Controls who can see the list of booked participants on the trip page.

Allowed:
string
length ≤ 60000

Optional message that appears in both the booking confirmation email and the payment confirmation page shown to participants.

string
enum
required

This setting allows you to choose how the payment fees are handled. The options are:
"credit_card" - Bank account payments are free to the participant, but if they choose to pay by credit card, a card fee is added to the price
"all" - all fees are paid by the participant
"service" - Service fees are paid by the participant. Payment method fees are covered by the organizer.
"none" - all fees are paid by the organizer

Allowed:
boolean
Defaults to false

Indicates whether the trip repeats on multiple dates instead of fixed start/end dates.

images
array of objects
required

Publicly accessible images displayed on the trip page.

images*
destination
object
required

Trip destination information (e.g., city, country, coordinates).

trip_options
array of objects
required

List of bookable trip packages or add-ons. Must include at least one package.

trip_options*
carbon_offset
object

Configuration for offering a carbon offset contribution on a trip.

contribution
object

Whether the participant is allowed to create a contribution / fundraising page after booking this trip.

waitlist
object

Whether the trip has a waitlist or not in case it’s sold out.

custom_brochure
object

Controls whether the trip displays a custom brochure and which brochure asset should be used.

esignature
object

Configuration for electronic signatures on a trip, including provider, signer requirements, and template settings.

paragraphs
array of objects

List of paragraphs displayed on the trip page.

paragraphs
included_items
array of objects

Items or services included in the trip price (e.g., meals, activities).

included_items
excluded_items
array of objects

Items or services excluded from the trip price (e.g., flights, insurance).

excluded_items
overviews
array of objects

High-level daily or sectional itinerary elements (e.g., Day 1, Day 2).

overviews
discounts
array of objects

Discount rules applied to the trip, such as early-bird or volume discounts.

discounts
departures
array of dates

List of trip start dates (ISO 8601 YYYY-MM-DD) for recurring trips. Required when recurring is true. Ignored when recurring is false.

departures
price_adjustments
array of objects

Price changes applied to the trip within a specific date range (increase or decrease).

price_adjustments
surveys
array of objects

Surveys participants may be required to complete (at checkout or after booking), with due/lock scheduling.

surveys
Responses

Updated 7 days ago

Language
Credentials
URL
LoadingLoading…
Response
Click Try It! to start a request and see the response here! Or choose an example:
application/json

Updated 7 days ago