Ticketing link format

For deep links, partners will provide the base URL (see Partner Configuration). The query parameters that we add to the URL will follow the Google Transit Ticketing Extension with a reduced set of parameters:

Field Name	Details
from_ticketing_stop_time_id	(Repeatable) Identifier of the stop at which the leg starts. For a particular stop time, this is the value of the stop_id of the departure station.
to_ticketing_stop_time_id	(Repeatable) Identifier of the stop at which the leg ends. For a particular stop time, this is the value of the stop_id of the destination station.
service_date	(Date, Repeatable) Service day of the trip. This field formats as a JSON array, containing the date with the following format string: YYYYMMDD
boarding_time	(ISO 8601, Repeatable) Date & Time of departure (departure_time) of the stop_time at which the leg starts. The time value of this field conforms to ISO 8601, with the following format string: YYYY-MM-DDThh:mm:ss±hh:mm Important: The timezone of the boarding_time is always in UTC.
arrival_time	(ISO 8601, Repeatable) Date & Time of arrival (arrival_time) of the stop_time at which the leg ends. The time value of this field conforms to ISO 8601, with the following format string: YYYY-MM-DDThh:mm:ss±hh:mm Important: The timezone of the arrival_time is always in UTC.
booking_token	(String) Optional field used to add additional data. This value comes from your Travel Transport API response and is appended to the ticketing deep link. The maximum booking_token length should be 100 characters. Trip lookup should still work without the booking token, but it can be used to maintain price consistency between Google Search results and the partner booking page.

All repeatable parameters are specified as a JSON array, where multiple values indicate transfer stops. You can find examples of the URL encoding in the examples of the Google Transit Ticketing Extension.