Partner configuration
Stay organized with collections
Save and categorize content based on your preferences.
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)
- 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.
Except as otherwise noted, the content of this page is licensed under the Creative Commons Attribution 4.0 License, and code samples are licensed under the Apache 2.0 License. For details, see the Google Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.
Last updated 2025-08-20 UTC.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-20 UTC."],[[["\u003cp\u003ePartners provide brand details, including short names and logos, localized by market.\u003c/p\u003e\n"],["\u003cp\u003ePartners specify GTFS feed names for which they will offer pricing and booking.\u003c/p\u003e\n"],["\u003cp\u003eServer configurations, including address, credentials, and supported queries per second (QPS), are required from partners.\u003c/p\u003e\n"],["\u003cp\u003ePartners must provide contact information for technical questions and issue escalation.\u003c/p\u003e\n"],["\u003cp\u003eAdditional specifications, including the name of the supplier and the web base URL for deep links, are required for stop-only integrations.\u003c/p\u003e\n"]]],[],null,["# Partner configuration\n\nFor the Partner Configuration, the partner provides information about\nthemselves. This is required for partners who want to include pricing and\navailability information in addition to schedule and route information. This\ninformation should be provided by emailing transport-help@google.com for manual\nconfiguration.\n\nThis information will include:\n\n- Brand information (localized by market):\n - Short partner brand name\n - Partner logo (see [Logo requirements](https://developers.google.com/travel/transport/guides/partner-integration/logos) for format and dimension requirements)\n- Integration Type: Bus or Rail.\n- Partner Server configuration --- the configuration for the servers that the partner implemented, including:\n - Server Address (HTTPS required, e.g., `https://api.partner.com/v1`)\n - Authentication: HTTP Digest or Certificate\n - Maximum supported queries per second (QPS)\n - We will use this information to determine support for future features such as throttling and caching\n - Recurring API downtimes.\n- Partner contact information (for technical questions and issue escalation relating to the integration)\n - Email\n- Deep links configuration\n - The web base URL.\n - Which of the `lang`, `cur` or `utm_source` parameters are supported by the booking site.\n- Integration type specific information:\n - GTFS based:\n - GTFS feed names: the names of the GTFS feeds for which a partner is providing pricing or booking functionality\n - Stop based:\n - The name of the supplier whose schedules the partner would like to price\n - List of stops in scope, with an unique ID and its geo coordinates\n- Bulk API options\n - Whether the partner would like to receive `known_itineraries` to optimize what they return to Google.\n - Whether to price direct or multi-segment, and how many segments to price.\n - Whether the partner would like to receive agency codes to identify operators that serve the same route at the same time."]]