# 511.org Transit Docs

## Docs

- [GTFS Feed Download](https://docs.bayareatransit.dev/api-reference/gtfs-&-bulk-feeds/gtfs-feed-download.md): Downloads a GTFS zip. Use `operator_id=RG` for the active regional feed. The optional `historic` month is in `YYYY-MM` format.
- [GTFS Operators](https://docs.bayareatransit.dev/api-reference/gtfs-&-bulk-feeds/gtfs-operators.md): Lists operators and agencies with GTFS feeds available for download. Description and parameter names come from the current transit page.
- [GTFS-Realtime Service Alerts](https://docs.bayareatransit.dev/api-reference/gtfs-&-bulk-feeds/gtfs-realtime-service-alerts.md): Service alerts for a single agency or the regional feed. The transit page says `agency` is optional and `format` is optional.
- [GTFS-Realtime Trip Updates](https://docs.bayareatransit.dev/api-reference/gtfs-&-bulk-feeds/gtfs-realtime-trip-updates.md): Realtime trip updates in Protocol Buffer format. Use `agency=RG` for the consolidated regional feed.
- [GTFS-Realtime Vehicle Positions](https://docs.bayareatransit.dev/api-reference/gtfs-&-bulk-feeds/gtfs-realtime-vehicle-positions.md): Realtime vehicle positions in Protocol Buffer format. Use `agency=RG` for the consolidated regional feed.
- [Real-time Stop Monitoring](https://docs.bayareatransit.dev/api-reference/realtime-siri/real-time-stop-monitoring.md): Realtime stop predictions. If `stopcode` is omitted, 511 may return all monitored stops for the agency and the PDF warns the response can take more than 5-7 seconds.
- [Real-time Vehicle Monitoring](https://docs.bayareatransit.dev/api-reference/realtime-siri/real-time-vehicle-monitoring.md): Realtime monitored vehicle activity for an agency, optionally filtered to a single vehicle. Based on transit spec section 2.11 and JSON example B.1.11.
- [Scheduled Departures at a Stop](https://docs.bayareatransit.dev/api-reference/realtime-siri/scheduled-departures-at-a-stop.md): SIRI StopTimetable for scheduled arrivals and departures within a time window. Current request parameter casing follows the public transit page; PDF details are in section 2.9.
- [Lines](https://docs.bayareatransit.dev/api-reference/static-netex/lines.md): Route list for a given operator. Based on transit spec section 2.2 and JSON example B.1.2.
- [Operators](https://docs.bayareatransit.dev/api-reference/static-netex/operators.md): Transit operator list. Based on transit spec section 2.1 and JSON example B.1.1.
- [Patterns](https://docs.bayareatransit.dev/api-reference/static-netex/patterns.md): Journey patterns for a line. Based on transit spec section 2.5 and JSON example B.1.5.
- [Route Timetable](https://docs.bayareatransit.dev/api-reference/static-netex/route-timetable.md): Timetables for a given line. The current page uses lowercase `includespecialservice` and `exceptiondate`; the PDF section 2.6 capitalizes those names. JSON example B.1.6.
- [Service Holidays](https://docs.bayareatransit.dev/api-reference/static-netex/service-holidays.md): Agency service exceptions and holiday dates. Based on transit spec section 2.7 and JSON example B.1.7.
- [Stop Places](https://docs.bayareatransit.dev/api-reference/static-netex/stop-places.md): Physical stop lookup with more detailed stop-place structure. Based on transit spec section 2.4 and JSON example B.1.4.
- [Stops](https://docs.bayareatransit.dev/api-reference/static-netex/stops.md): ScheduledStopPoint lookup for an operator. Based on transit spec section 2.3 and JSON example B.1.3.
- [Bulk feeds](https://docs.bayareatransit.dev/bulk-feeds.md): GTFS, GTFS-Realtime, GTFS+ companion files, and historic regional feed notes.
- [Overview](https://docs.bayareatransit.dev/index.md): Web-native documentation for the public 511.org transit APIs and supporting source material.
- [Pathways coverage](https://docs.bayareatransit.dev/pathways.md): Stations and hubs explicitly listed as covered by pathways data.
- [Realtime data](https://docs.bayareatransit.dev/realtime-data.md): SIRI-based stop and vehicle state, plus discontinued and future-looking service families.
- [Request basics](https://docs.bayareatransit.dev/request-basics.md): Authentication, formats, rate limits, common errors, and request-construction quirks.
- [Source documents](https://docs.bayareatransit.dev/source-documents.md): Local copies of the official PDFs and what each document contributes to the transit documentation set.
- [Static data](https://docs.bayareatransit.dev/static-data.md): The scheduled network model: operators, lines, stops, patterns, timetables, holidays, and shapes.
- [Usage policy](https://docs.bayareatransit.dev/usage-policy.md): License scope, attribution, branding restrictions, disclaimers, and operational obligations.

## OpenAPI Specs

- [511-transit-openapi](https://docs.bayareatransit.dev/openapi/511-transit-openapi.json)
- [openapi](https://docs.bayareatransit.dev/api-reference/openapi.json)

## Optional

- [511 Transit Page](https://511.org/open-data/transit)