# Partner configuration

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](https://developers.google.com/travel/transport/guides/partner-integration/logos) 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 (one of):
    - HTTP Digest
    - Client Certificate
    - OAuth 2.0
  - 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 Email (for technical questions and issue escalation relating to the integration)
- URL targets:
  - The URL of the partner site.
  - The base URL for [ticketing links](https://developers.google.com/travel/transport/guides/partner-integration/ticketing-links).
  - The base URL for [search links](https://developers.google.com/travel/transport/guides/partner-integration/search-links).
- 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.

> [!NOTE]
> **Note:** The number of required URL targets varies. Depending on your business model, you may only need to implement one or two. Please reach out to transport-help@google.com to confirm the requirements for your account.