Webhooks

WeTravel's webhooks allow enterprise clients and software partners to build into our platform. They inform users about events happening on WeTravel, so they can update their internal systems with this information.

Enable Webhooks

By default, webhooks are disabled for all accounts. To enable them go to the Profile --> Edit Profile, find the "Webhooks" section and click the "Yes" button.

NOTE: You will first need to generate an API key in order to see the "Webhooks" section in your profile page.

2098

Webhooks Enabled

Add New Endpoint URL

After enabling webhooks, click on "Manage Webhooks" to add an endpoint URL. Another window will open where you can add an endpoint by clicking on the button on the top right "+ Add Endpoint"

2232

Endpoint List

When you add a new endpoint, you can configure it to listen for a specific event or all events.

1668

Endpoint Configuration

You can add multiple webhook endpoints that can listen for events.

3036

Endpoint List

You can edit, delete or disable existing endpoints by clicking on them and making changes in the subsequent endpoint manager.

2264

Endpoint Manager

Event Types

You may use webhooks to receive events, such as booking created and updated. All the events are grouped into event types which can be subscribed to. A list of all event types with a detailed structure and examples can be found on the "Manage Webhooks" page under the "Event Catalog" menu button.

Supported Event Types

NameDescriptionTriggers
booking.createdThis event is fired when a new booking is created.
  • New Booking on trip page or embedded widgets
    - New booking in "Manage Trip" by using "Add Participant"
booking.updatedThis event is fired when a booking is updated.
  • Departure date is changed
    - Refund is issued
    - Booking is canceled
    - Booking is updated by using "Add Participant"
    - Participant updates their information provided
    - New custom price is set
    - Package is switched
    - Bulk action is initiated
    - eSignature is received
    - New payment is made
    - Payment failed or disputed
    - Trip details are updated
    - Balance due adjusted
    - A rebooking is initiated, and the original booking is canceled
payment.createdThis event is fired when a new payment is made.
  • A new payment is initiated
payment.updatedThis event is fired when a payment is updated.
  • Payment status changes from pending to successful or failed
    - Payment status changes from successful to refunded or disputed
    - A rebooking occurs, and the payment details are transferred to the new trip.
transaction.createdThis event is fired when a new transaction occurs.
  • Payment is received
    - Refund is initiated
    - Dispute is processed
    - Payout is initiated
    - Instant payout is initiated
    - Card transfer is initiated
    - Vendor payment is initiated
    - Wire Transfer is initiated
    - Top-up payment is received
    - Balance is adjusted by WeTravel
transaction.updatedThis event is fired when a transaction is updated.
  • A rebooking occurs, and the transaction details are transferred to the new trip.
trip.publishedThis event is fired when a new trip is published.
  • A trip is published in the WeTravel trip builder
    - A trip is published through the WeTravel "Trip Builder" API.
lead.createdThis event is fired when a new lead is created.
  • A brochure is downloaded from the website
    - A brochure is downloaded from the trip page - Question is asked in Trip page - Question is asked in Profile page
lead.updatedThis event is fired when a lead gets updated.
  • A brochure is downloaded by the same lead from the website
    - A brochure is downloaded by the same lead from the trip page
    - Another Question is asked by the same lead in Trip page
    - Another Question is asked by the same lead in Profile page