Skip to main content

Redirecting booking confirmation data

OnceHub allows you to send booking confirmation data to the redirect page via URL parameters. Every time a booking is successfully scheduled, the booking form submission data and information about the booking that was scheduled will be converted into key-value pairs (KVPs) and appended to the redirect URL.

This feature can be used to create a custom confirmation page, enable client-side integrations, or enrich customer data profiles, among other applications.

Set up Automatic redirect with booking confirmation data​

In order to send booking confirmation data to your redirect page, you must enable the Automatic redirect feature from the Redirect settings section of your Booking calendar:

  1. Turn Automatic redirect to ON.
  2. Enter the URL of your redirect page.
  3. Click the checkbox to Send booking confirmation data to redirect page.
  4. Click Save to apply these settings to your Booking calendar.

That's it! You have enabled redirecting booking confirmation data to your specified page via URL parameters.

Example URL with booking confirmation data​

The following is an example of a URL containing booking confirmation data that is sent to the redirect page:

http://www.example.com/?booking_calendar=BKC-8D6NGQEM5G&subject=Meeting+with+Sales&status=scheduled&customer_timezone=Asia%2FKolkata&id=BKNG-2R5C3TQBX1PZ&creation_time=2025-07-17T10%3A17%3A10.765Z&starting_time=2025-07-18T11%3A00%3A00.000Z&name=Carrie+Customer&email=Carrie-Customer%40staticso2.com&company=Acme&meeting_reason=Product+Demo

Booking confirmation data sent via URL parameters​

Two types of booking confirmation data will be sent to your redirect page via URL parameters:

  1. Booking form submission data - Customer information submitted to the booking form
  2. Booking data created when scheduling - System-generated data about the booking

Booking form submission data​

Customer information submitted to the booking form will be added as URL parameters and sent to the custom confirmation page URL upon redirect. Any booking form field (including custom fields) for which the customer has submitted data will be added to the redirect URL. Empty booking form fields will not be added to the redirect URL.

The following table contains the parameter name and description of the fields sent:

Parameter nameDescription
nameThe name provided by the customer in the booking form.
emailThe email provided by the customer in the booking form.
phoneThe phone number provided by the customer in the booking form.
<custom field name>The name of the user-defined custom field (uses the mapped field name).

How are custom fields handled?​

Custom fields for which the customer enters booking submission data will be added to the URL when booking confirmation data is sent to the redirect page.

The custom field parameter name is the Mapped field name as configured in your booking calendar's form settings.

Booking data created when scheduling​

Booking data that is created when a new booking is scheduled will be added as URL parameters and sent to the redirect page.

The following table contains the parameter name and description of the fields sent:

Parameter nameDescription
booking_calendarThe ID of the booking calendar used to make the booking.
idThe unique ID of the booking.
subjectThe subject of the booking calendar.
statusThe status of the booking (e.g., scheduled).
creation_timeThe date and time when the booking was created, in UTC.
starting_timeThe starting date and time of the booking, in UTC.
customer_timezoneThe time zone selected by the customer when making the booking.

Constraints​

The following constraints are important to keep in mind when redirecting booking confirmation data:

  • Booking confirmation data will only be sent to the redirect page when a booking is scheduled (not canceled, rescheduled, or reassigned).
  • OnceHub does not impose length limits for fields passed in the redirect URL. If the length of the query string exceeds the URL character limit, the URL will be truncated and some data may not be sent.

All datetime values are sent in ISO 8601 format in UTC.