📣 What's New

Welcome to the product hub for our API! This is your go-to place to stay informed about the latest features, enhancements, and important updates we're rolling out. We're constantly working to improve your experience and expand the capabilities of our platform. Check back often to see what's new!

Unified Support for Alternative Station Identifiers

Nov 25, 2025

To provide greater flexibility when integrating with external travel systems, we’ve introduced a new conceptual framework for Alternative Station Identifiers. This enhancement allows you to use a wider variety of industry-standard codes—such as UIC, IATA, and other third-party identifiers—interchangeably across our API. This unified approach simplifies the mapping process between your internal databases and our platform, ensuring more reliable search and booking workflows when working with diverse data sources. For more details on implementation, please refer to our Alternative Station Identifiers guide.

Introducing the Retailer Agent

Sep 18, 2025

We are thrilled to announce the launch of our new Retailer Agent. This powerful AI tool is designed to guide your customers through the entire pre-sales journey, from searching for connections to completing a booking. The Retailer Agent acts as a virtual assistant, helping users find routes, compare options, and navigate the booking process in a conversational manner. Enhance your user experience and boost conversions by providing instant, automated assistance. For more details, please see the complete Retailer Agent documentation and contact your Partnership Manager to enable this advanced feature.

Introducing our MCP Server

Jul 29, 2025

We are excited to introduce our new Retailer API MCP Server, an implementation designed to wrap the functionalities of Distribusion's Retailer API. This server is intended for use by AI Agents or Agentic applications that support MCP communication, operating in a server-to-server fashion. It exposes various tools, including search_stations, search_cities, search_areas, connections_find, connections_vacancy, get_checkout_link, price_calendar, and get_carrier_info, each corresponding to a Retailer API endpoint. To learn more about connecting and utilizing this enterprise API feature, please refer to its dedicated documentation and contact your Partnership Manager for access.

Search by UIC and IATA Codes

Jul 17, 2025

We've expanded our search capabilities to allow querying connections using industry-standard IATA airport codes and UIC train station codes. This enhancement provides greater flexibility for integrations and caters to various search preferences, especially for European rail stations. For more details on how to implement these search methods in /connections/find, please refer to the IATA and UIC Codes Search guide.

Search by Geo Coordinates

Apr 1, 2025

You can now search for available connections using precise geographic coordinates (latitude and longitude with a defined radius), moving beyond reliance on predefined station lists. This feature is particularly useful when your users have exact locations (e.g., a hotel address) as part of their search in /connections/find, or if you prefer to use your own stored location data. To understand how to implement this, please refer to the Geo Coordinate Search guide.

Introducing the Post-Sales AI Bot

May 12, 2025

You can now elevate your customer support by integrating our new Post-Sales AI Bot, designed to power intelligent post-sales chatbots without requiring you to build the AI. This enterprise feature automates Level 1 support by enabling your chatbot to understand and answer common, booking-specific customer queries in multiple languages—from retrieving booking details and station locations to providing luggage policies and cancellation information. To learn more about its capabilities and how to get started, please check our Post-Sales AI Bot guide. Reach out to your Partnership Manager to unlock this advanced feature.

Easily Handle Dynamic Passenger Data Requirements

May 9, 2025

To help you streamline bookings across various carriers, we've introduced enhanced ways to dynamically determine required passenger information. As different carriers often have unique data needs (like name, date of birth, or document details), you can now ensure successful bookings and improve user experience. Simply fetch carrier-specific passenger field requirements in advance using the new /marketing_carriers/{marketing_carrier_id}/booking/schema endpoint, or retrieve these details dynamically within your booking flow from the /connections/vacancy and /reservations/create endpoint responses. Integrating this allows you to adapt your forms and validation on the fly, reducing errors and ensuring compliance. For full details, please see the Dynamic Passenger Details guide.

Enhanced Search Precision with Departure Times for Return Trips

Mar 19, 2025

You can now offer more precise search results for round trips by specifying desired departure time windows for the return journey. Complementing the existing departure_start_time and departure_end_time parameters available for the initial leg in /connections/find endpoint, we've introduced return_start_time and return_end_time . Using these new parameters allows users to narrow down their return travel options to specific times of day, significantly improving the search experience, especially for carriers with extensive offerings like Deutsche Bahn. Integrate these parameters into your search requests to provide more targeted and convenient results. Find out more it in our Serching for Trips guide.

UIC Codes Now Available for European Rail Stations

January 16, 2025

We've enhanced our station data by adding UIC (International Union of Railways) codes for European rail stations. These unique identifiers can help simplify mapping to other systems and provide a familiar, industry-standard reference. You'll find the uic_station_code attribute directly within the station object in responses from the /stations and /stations/{station_code} endpoints for relevant stations. For more details on UIC and other external location codes, please see the Preparing Metadata guide.

New leg_type Field in Search Responses

Nov 8, 2024

We've added a leg_type field as an attribute to /connections/find search responses, clearly labeling each leg as "outbound" or "inbound". This human-readable parameter simplifies your integration by removing the need for custom logic to determine journey direction and is consistently present for all trips. This enhancement makes directional information easier to use directly from the API.