---
title: "Create trip"
method: POST
path: "/draft_trips"
tags: ["Trips"]
---

# Create trip

`POST /draft_trips`

Creating a "draft" trip object. Using the other endpoints of Trip builder you can enhance your trip object and eventually publish it.

## Request body

- object
  - `data` CreateTrip — Trip object for creation
    - `trip_id` string — Allows you to set the optional trip reference. It is not visible to your clients, it is only visible to you in your WeTravel dashboard and reporting.
    - `url` string — Allows you to set the URL of the trip on WeTravel
    - `title` string, required — Allows you to set the title of the trip
    - `destination` string, required — Allows you to set the destination of the trip in free-form text.
    - `start_date` string, required — Allows you to set the start date of the trip in ISO 8601 format, e.g. “2021-05-07”
    - `end_date` string, required — Allows you to set the end date of the trip in ISO 8601 format, e.g. “2021-05-07”
    - `group_min` integer, required — Allows you to set minimum group size for the trip
    - `group_max` integer, required — Allows you to set the maximum group size for the trip
    - `currency` 'USD' | 'EUR' | 'CAD' | 'ZAR' | 'GBP', required — Allows you to set the currency in which the payments are accepted for the trip
    - `participant_list_show_type` 'everyone' | 'participants' | 'only_organizer', required — Allow you to choose how to show the names of already booked participants on your booking page. The available options are “everyone”, “participants” or “only_organizer” which stand for everyone - everyone can see the participant list on the booking page participants - only already booked participants see the participant list only_organizer - nobody can see the participant list (only the organizer)
    - `welcome_message` string — Allow you to set a welcome message that is added to the booking confirmation email and is also shown on the payment confirmation page. This field can also contain HTML tags such as \<p\>, \<b\>, \<i\>, \<strong\>, \<a\> for formatting.
    - `participant_fees` 'credit_card' | 'service' | 'all' | 'none', required — Allows you to choose how the payment fees are handled. The available options are: “credit_card” - Bank account payments are free for the participant, but if they choose to pay by credit card, a card fee is added to the price “service” - Service fees are paid by the participant. Payment method fees are covered by the organizer. “all” - all fees are paid by the participant “none” - all fees are paid by the organizer
    - `listing_status` 'private' | 'public', required — Allows you to set whether the trip is “public” or “private”. Public trips can be indexed by search engines; however, private ones cannot.
    - `waiting_list_enabled` boolean, required — Allows you to set whether the trip has a waitlist or not in case it’s sold out.
    - `can_contribute` boolean, required — Allows you to set whether the participant is allowed to create a contribution / fundraising page after booking this trip.
    - `carbon_offset` CarbonOffset — Carbon Offset Contribution
      - `enabled` boolean, required — Carbon Offset Contribution offered for the trip
      - `percentage` number, required — Carbon Offset Contribution amount as a selected percentage of the trip price
      - `paid_by_participant` boolean, required — Carbon Offset Contribution is paid by participant

## Response `201`

Successfully created

- object
  - `data` Trip — Trip object
    - `title` string — Trip title

## Other responses

- `400` — Bad Request
- `401` — Unauthorized

---

[API](https://skmtc.net/wetravel/apis/authentication-api.md) · [All operations](https://skmtc.net/wetravel/apis/authentication-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/wetravel/authentication-api/versions/5c747875f084/schema)