# Guidelines for feed delivery

This guide describes how to provide your Micromobility feed to Google after it's
generated. For a description about how to create your feed, refer to the
specifications in the [Reference](https://developers.google.com/micromobility/reference/introduction) tab.

## Feed guidelines

As part of the process to send your generated Micromobility feed to Google, be
aware of the following process and guidelines:

- Ensure that the bike availability and dynamic fare data, where applicable,
  are up-to-date. To do so, you must upload a new feed version to the GBFS feed
  host every 30 seconds. Also, the latency to retrieve the data must not exceed
  30 seconds.

- To deliver your feed to Google, you must support HTTP GET.

### Feed delivery with HTTP GET

Google fetches the feed from the configured location with an `HTTPS GET`
request and supports the following authentication methods:

- **HTTP Digest Authentication:** If you implement this, email the configured username and password to [Micromobility partner support](mailto:micromobility-partner-support@google.com).
- **Custom HTTP header fields:** For this to be supported, as part of your request to Google, send the required header fields and values that you need.
- **GET parameters:** If additional GET parameters are required, add them to the host address before you email it to [Micromobility partner support](mailto:micromobility-partner-support@google.com).

To optimize file size during transfer, Google supports gzip compression in the
HTTP header. Specifically, Google sends `Accept-Encoding: gzip, deflate` in
the `HTTP` request header and accepts the response with the `HTTP` header
`Content-Encoding: gzip`.

After you determine the host location and details, email the configuration
details to [Micromobility partner support](mailto:micromobility-partner-support@google.com).

### Feed sharding

To *shard* a feed is to break the whole feed into multiple non-intersecting
subsets. Depending on your backend systems, fleet types, and sizes,
sharding might be necessary.

For technical details on when and how to shard your feed, refer to
[Feed sharding](https://developers.google.com/micromobility/reference/sharding) in the Reference section.

Google will use the same mechanism to fetch both sharded and unsharded feeds as
described in [Feed delivery with HTTP GET](https://developers.google.com/micromobility/guides/guidelines-for-feed-delivery#feed-delivery-with-http-get).

After you determine the host location and details for each shard, email the
configuration details of each shard along with the metro areas that the shard
covers to [Micromobility partner support](mailto:micromobility-partner-support@google.com).