Partner configuration

  • Partners provide brand details, including short names and logos, localized by market.

  • Partners specify GTFS feed names for which they will offer pricing and booking.

  • Server configurations, including address, credentials, and supported queries per second (QPS), are required from partners.

  • Partners must provide contact information for technical questions and issue escalation.

  • Additional specifications, including the name of the supplier and the web base URL for deep links, are required for stop-only integrations.

For the Partner Configuration, the partner provides information about themselves. This is required for partners who want to include pricing and availability information in addition to schedule and route information. This information should be provided by emailing transport-help@google.com for manual configuration.

This information will include:

  • Brand information (localized by market):
    • Short partner brand name
    • Partner logo (see Logo requirements for format and dimension requirements)
  • Integration Type: Bus or Rail.
  • Partner Server configuration — the configuration for the servers that the partner implemented, including:
    • Server Address (HTTPS required, e.g., https://api.partner.com/v1)
    • Authentication: HTTP Digest or Certificate
    • Maximum supported queries per second (QPS)
      • We will use this information to determine support for future features such as throttling and caching
    • Recurring API downtimes.
  • Partner contact information (for technical questions and issue escalation relating to the integration)
    • Email
  • Deep links configuration
    • The web base URL.
    • Which of the lang, cur or utm_source parameters are supported by the booking site.
  • Integration type specific information:
    • GTFS based:
      • GTFS feed names: the names of the GTFS feeds for which a partner is providing pricing or booking functionality
    • Stop based:
      • The name of the supplier whose schedules the partner would like to price
      • List of stops in scope, with an unique ID and its geo coordinates
  • Bulk API options
    • Whether the partner would like to receive known_itineraries to optimize what they return to Google.
    • Whether to price direct or multi-segment, and how many segments to price.
    • Whether the partner would like to receive agency codes to identify operators that serve the same route at the same time.