Skip to content
  • There are no suggestions because the search field is empty.

Usage Guide: Automatically Add or Update a registered person on a trip using addregistration API endpoint or Zapier

Sometimes people register to book from another platform, add them (or update them) automatically using this API endpoint.

Available Plans: PRO and above

For this endpoint, "invitee" refers to the traveler registered on the trip. You can get the inviteeId from registration webhooks or the getinvitee endpoint.

https://youlivetotravel.github.io/youli-doco/

This endpoint can be accessed either directly via the API or through Zapier.

Add or Update Registration

You can do this via the UI from Trip CRM, or use this endpoint directly or via Zapier to add a person as registered to a TRIP in YouLi.

While registration is required to book, creating the registration only makes them booked if:

  • The package they are registered on is $0 or they have a personalized price of $0
  • They have made a payment
    • You can also add a manual payment via API if one has been made
    • Or they can click to the invoice generated by the registration from the confirmation email that is automatically send

POST /api/trip/addregistration

  1. tripId 
    1. Required
  1. email
    1. Required
    2. Zapier: Required
    3. Must be a valid email

  2. ForceNewRegistration (boolean)

    • When true, skip the existing "match by email" lookup entirely and always create a new invitee, even if the email already exists on the trip.

    AllowEmptyEmail (boolean)

    • When true, Email is no longer a required field.
    • The match-by-email lookup is only skipped when the email is actually blank (i.e. this flag relaxes the required-field rule; it doesn't change matching behavior when a real email is supplied). If AllowEmptyEmail=true and a non-blank email is sent that matches an existing invitee, normal update behavior still applies. That behavior shall be controlled by ForceNewRegistration, not AllowEmptyEmail.

    InvitationGroup (string)

    • If an invitation group with this name already exists on the trip, add the invitee to it.
    • If it doesn't exist, create a new invitation group with this name, default to "Paying Together", and add the invitee to it.
    • If not provided, don't touch the invitee's group assignment.
      • If they’re already in a group, leave them there
      • If they’re NOT, leave them as solo traveler
    • Value returned in the response as InvitationGroup

    ReservationNumber (string)

    • Reservation is not scoped to a single trip: a tour can be structured as a Main Tour with an optional linked Pre-Trip and Post-Trip, and a Reservation can span gangs across all three. When resolving ReservationNumber, if the trip being registered against is a Main Tour, a Pre-Trip, or a Post-Trip, the lookup will also search on the other linked trips
    • If a match is found (on the current trip or either linked trip), attach the invitee to that existing reservation.
    • If the provided value doesn't match any reservation on the current trip or its linked pre/post trips, return a 400 with alert email sent: "Reservation number {value} not found".
    • Ignored if IsNewReservation is also set (see below).

    IsNewReservation (boolean)

Troubleshooting

Any detailed errors will be sent to email configured on the account to receive API errors

Request