Partial Integration
With Distribusion partial integration, you will handle the search.
You have three ways of handling the search:
- Build your search engine using our APIs. We don't recommend this option if you only work with us, since our booking engine already provides a fully featured search experience.
- Integrate our Search SDK: a JavaScript SDK that allows you to have the search box on your website. If you use the Search SDK, the user will be redirected to the Distribusion booking engine for the search results and checkout.
- Specific landing pages: on most websites, some landing pages already have predefined Origins and Destinations. In this case, you can redirect the user directly to the search results page with the appropriate URL parameters.
Redirecting to Search Results Page
Search result page URL example https://book.distribusion.com/result?arrivalCity=GBBHX&departureCity=GBLON&locale=en&pax=1&retailerPartnerNumber=222222
URL Parameters
Mandatory Parameters
Parameter | Description | Type |
| Departure point. Choose one of the options. E.g., | Mandatory - String |
| Arrival point. Choose one of the options. E.g., | Mandatory - String |
| Your Distribusion account number (6 digits). | Mandatory - Integer |
Optional Parameters
Location & Carrier
Parameter | Description | Type |
| Filter the list of carriers to return in the search results. | Optional - Array |
| Return trip marketing carrier code. E.g., | Optional - String |
| Train type filter code. E.g., | Optional - String |
Date & Time
Parameter | Description | Type |
| Departure date for the trip in ISO 8601 format | Optional - String |
| Outbound departure time (HH:mm, 24h). E.g., | Optional - String |
| Latest outbound departure time (HH:mm, 24h). E.g., | Optional - String |
| Outbound arrival date (YYYY-MM-DD). E.g., | Optional - String |
| Outbound arrival time (HH:mm, 24h). E.g., | Optional - String |
| Return date for the trip in ISO 8601 format | Optional - String |
| Return trip departure date (YYYY-MM-DD). E.g., | Optional - String |
| Return trip departure time (HH:mm, 24h). E.g., | Optional - String |
| Return trip arrival date (YYYY-MM-DD). E.g., | Optional - String |
| Return trip arrival time (HH:mm, 24h). E.g., | Optional - String |
| Earliest return departure time (HH:mm, 24h). E.g., | Optional - String |
| Latest return departure time (HH:mm, 24h). E.g., | Optional - String |
Passengers & Pricing
Parameter | Description | Type |
| Number of passengers. E.g., | Optional - Integer |
| Passenger type code. E.g., | Optional - String |
| Number of passengers of this type. E.g., | Optional - Integer |
| The maximum age in the group of passengers. E.g., | Optional - Integer |
| Discount cards (comma-separated or JSON). E.g., | Optional - String |
| Cards per passenger (JSON or URL-encoded string). E.g., | Optional - String |
| Outbound fare class code. E.g., | Optional - String |
| Return fare class code. E.g., | Optional - String |
| Maximum price filter. E.g., | Optional - Float |
| Travel class code. E.g., | Optional - String |
Sorting & Filtering
Parameter | Description | Type |
| Sorting method. Accepted values: | Optional - String |
| Only show fastest connections ( | Optional - Boolean |
| Express search mode — automatically finds available trips ( | Optional - Boolean |
| Only show available trips ( | Optional - Boolean |
| Minimum transfer time in minutes. E.g., | Optional - Integer |
Stopover & Via Parameters
Parameter | Description | Type |
| Stopover station codes (comma-separated). E.g., | Optional - String |
| Outbound stopover station codes (comma-separated). E.g., | Optional - String |
| Inbound stopover station codes (comma-separated). E.g., | Optional - String |
| Via inclusion/exclusion rules (JSON or URL-encoded). Keys are station codes, values are | Optional - String |
| Via rules for outbound leg (same format as | Optional - String |
| Via rules for inbound leg (same format as | Optional - String |
| Dwell times at via stations in minutes (JSON or URL-encoded). Keys are station codes, values are minutes. E.g., | Optional - String |
| Dwell times for outbound vias (same format as | Optional - String |
| Dwell times for inbound vias (same format as | Optional - String |
Display & UI
Parameter | Description | Type |
| Display mode for the booking engine UI. Accepted values: | Optional - String |
| Language code for the UI. A two-letter or four-letter code is accepted, like | Optional - String |
| Currency code for the UI. Three-letter ISO currency code, like | Optional - String |
| Timezone in IANA format. E.g., | Optional - String |
| Hide location selection in the UI ( | Optional - Boolean |
| Hide ticket details in the UI ( | Optional - Boolean |
| Display results in timetable view ( | Optional - Boolean |
| Enable weekly trip search mode ( | Optional - Boolean |
Seat Selection
Parameter | Description | Type |
| Enable seat reservation mode ( | Optional - Boolean |
| Pre-selected seat assignments (JSON or URL-encoded object). Structured as a nested object keyed by connection type ( | Optional - String |
Offers & Experiments
Parameter | Description | Type |
| Offer codes (comma-separated). E.g., | Optional - String |
| Offer IDs (comma-separated). E.g., | Optional - String |
| Experiment identifier. Used to assign the user to a specific A/B test experiment. E.g., | Optional - Integer |
Booking & Contact
Parameter | Description | Type |
| Booking identifier. E.g., | Optional - String |
| Retailer booking reference. E.g., | Optional - String |
| Pre-filled customer email address. E.g., | Optional - String |
| Pre-filled customer phone number. E.g., | Optional - String |
Season Ticket
Parameter | Description | Type |
| Enable season ticket search mode ( | Optional - Boolean |
Integration & Technical
Parameter | Description | Type |
| Parent domain for | Optional - String |
| URL to redirect the user to after booking. Must be a valid | Optional - String |
| SEO pre-rendering mode ( | Optional - Boolean |
Notes
- Boolean values are case-insensitive (
true,false,1,0are accepted). - Dates must be in
YYYY-MM-DDformat. - Times must be in
HH:mm24-hour format. - For parameters accepting JSON or arrays, use URL encoding (e.g.,
encodeURIComponent). - Multiple values (e.g., for
cards,offers) can be comma-separated. - Past departure dates are automatically normalized to today's date.
- If
returnDateis set beforedepartureDate, it will be adjusted to the day after departure. - The
retailerPartnerNumberis required — requests to/resultwithout it will be redirected to a 404 page. - UTM tracking parameters (e.g.,
utm_source,utm_medium,utm_campaign) are automatically captured and forwarded for analytics.
What made this section helpful for you?
What made this section unhelpful for you?
On this page
- Partial Integration