API

Sections

Theme switcher

Required Passenger Detail

When creating or confirming a reservation, retailers must include the passenger's real and accurate information. It is crucial to use the actual customer's details (e.g., first and last names, email address, government ID) in the /reservations/create and /reservations/confirm requests, rather than using dummy data or an agent's booking email.

Why Accurate Details are Required

Providing accurate passenger information is essential for several reasons:

  1. Customer Communication: Correct contact details are required for notifying the customer in the case of cancelled trips or disruptions to their journey.
  2. Identity Verification: For some carriers, such as KAI and China Railway, accurate passenger information is mandatory for their identity verification process.
  3. Preventing Booking Failures: Supplying incorrect details may result in booking failures.

Address Details

While the requirement for accurate contact and identity information is strict, there is more flexibility regarding passenger address details (street, city, country, zip code). It is always best practice to provide accurate address information when possible. However, if these details are not collected in your booking flow, it is generally acceptable to use placeholder data for these specific fields. This is because most carriers do not use address data for operational purposes, with the main exception being for customer invoice generation.

Was this section helpful?

What made this section unhelpful for you?

On this page
  • Required Passenger Detail
View as Markdown

Ask an AI

Open in ChatGPTOpen in ClaudeOpen in Perplexity

Code with AI

Open in Copilot