Skip to main content
GET
/
transit
/
StopMonitoring
Real-time Stop Monitoring
curl --request GET \
  --url 'https://api.511.org/transit/StopMonitoring?api_key='
{
  "Siri": {
    "ServiceDelivery": {
      "StopMonitoringDelivery": {
        "MonitoredStopVisit": [
          {
            "RecordedAtTime": "2026-03-25T12:01:00-07:00",
            "MonitoringRef": "18079",
            "MonitoredVehicleJourney": {
              "LineRef": "49",
              "MonitoredCall": {
                "ExpectedArrivalTime": "2026-03-25T12:04:00-07:00",
                "AimedArrivalTime": "2026-03-25T12:02:00-07:00"
              }
            }
          }
        ]
      }
    }
  }
}

Documentation Index

Fetch the complete documentation index at: https://docs.bayareatransit.dev/llms.txt

Use this file to discover all available pages before exploring further.

Authorizations

​
api_key
string
query
required

511.org token query parameter.

Query Parameters

​
format
enum<string>
default:json

Desired response format. JSON is the default when omitted.

Available options:
json,
xml
​
agency
string
required

Agency identifier for SIRI and GTFS-RT endpoints.

​
stopcode
string

Current transit page casing for stop filtering. The PDF section 2.10 shows 'stopCode'.

Response

Realtime monitored stop visits in SIRI JSON or XML.

The response is of type object.