Open Data FAQ

511 SF Bay, the free regional traveler information program managed by the Metropolitan Transportation Commission (MTC), currently offers transit and traffic event data through a number of standardized data feed and API endpoints. These open data services are provided to anyone with a valid API key. A single API key can be used with all data endpoints available through the http://api.511.org domain.

An API key can be requested by submitting this form. Once your email address is verified, a key will be issued. You will need to use that key with your desired data endpoints to receive data.

The default limit is 60 requests per 3600 seconds per API key. Rate limit can be increased based on the need of the use case. To request an increased rate limit, please contact transitdata@511.org with the following information:

• your API key

• the rate limit you need

• a description of the use case

• data endpoints you intend to use

• a brief justification for the requested rate limit

Relevant technical specifications for transit and traffic data feeds and APIs can be found at the bottom of transit and traffic open data pages. These documents are kept up to date as and when changes to data feed and API endpoints are deployed in production.

We recommend that our data consumers first review transit and traffic technical specifications, and look for their questions in this FAQs. If further help is needed, please send an email to our Google group at 511developerresources@googlegroups.com. Someone will respond as soon as possible.

All transit service operators currently in the 511 system and their IDs can be queried from the http://api.511.org/transit/operators?api_key={your_key}. Couple of things to note in the response of this API:

1. Operators with IDs 5E, 5F, 5O, and 5S are used internally by the 511 system and has no transit service data associated with them. 5E may be used to provide information during regional emergencies.

2. A ‘true’ value in the <Monitored> tag means that the operator provides real-time data as well.

You can find all line ID and name for an operator from the http://api.511.org/transit/lines?api_key={your_key}&Operator_id={operatorID} API. For more detail and available filters, please review the 511 Transit data feed and API specification available here: Open 511 Data Exchange Specification v1.30 - Transit.

To get an active timetable for a desired transit route, you need to send a request using the timetable API as below. http://api.511.org/transit/timetable?api_key={your_key}&operator_id={operatorID]&line_id={lineID}. Desired operatorID and lineID can be obtained from the APIs mentioned above. For more detail and available filters for the timetable API, please review the technical specifications.

The group of APIs exposed under the http://services.my511.org/… domain was our previous edition of custom real-time transit APIs. These APIs are set to expire sometime later this year and new tokens are not generated for these APIs. If you have received a new token by submitting a request form available at http://511.org/open-data/token, your token will only work with the new open 511 transit and traffic APIs.

511 open data currently does not include any transit services in the Bay Area that are provided by operators based outside of the region.

511 SF Bay includes transit services based in the San Francisco Bay Area that are open to public and operate on a published schedule. Transit operators are required to provide data to the 511 SF Bay system following a protocol in a timely manner. Some private ferry services are currently not able to provide their data in a timely manner following the required protocol. As and when these ferry operators are able to provide data fulfilling 511 SF Bay’s requirements, data will become available through our system.

There are numerous shuttle services in the San Francisco Bay Area - some with scheduled service, and some are flexible. Shuttles with scheduled services that provide data to 511 SF Bay are made available through 511 open data.

Currently no ferry or shuttle services provide real-time data to 511 SF Bay.

511 SF Bay program covers all freeways and state highways in the San Francisco Bay Area. The traffic event API provides active incidents and planned events on those roadways. Detail technical specification of the traffic event API can be downloaded from here.

Regional GTFS feed combines all transit agencies’ GTFS feeds available to the 511 SF Bay system to create a single feed for the San Francisco Bay Area region. Each morning, the Regional Feed is produced from the active versions of agency GTFS feeds produced by http://api.511.org. Any data change for any of the transit services that would be effective on that day is incorporated into the Regional GTFS feed. Regional GTFS feed is refreshed at 6:00 a.m. PT each morning.

Regional GTFS feed can be downloaded by using 511 SF Bay’s Data Feed API and setting the operator_id filter value to ‘RG’. Following is the URL to download the Regional Feed:

http://api.511.org/transit/datafeeds?api_key={your-key}&operator_id=RG

Yes, Historic Regional GTFS feed is also available by month starting from January 2020. It can be downloaded by setting the historic parameter to desired year and month with the operator_id parameter set to ‘RG’. Following is an example to download historic feed:

 http://api.511.org/transit/datafeeds?api_key={your-key}&operator_id=RG&historic=2020-03

Yes, pathways data is now available as part of the Regional GTFS Feed for all of Bay Area transit hubs as listed here.

Yes, fares 2.0 data is now available as part of the Regional GTFS feed for the transit agencies included in the 511 SF Bay system. Currently, this data is published in beta version. We appreciate any feedback you may have on this data.