> ## 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.

# Stops

> ScheduledStopPoint lookup for an operator. Based on transit spec section 2.3 and JSON example B.1.3.



## OpenAPI

````yaml /openapi/511-transit-openapi.json get /transit/stops
openapi: 3.1.0
info:
  title: 511.org Transit API Reference
  version: docs-snapshot-2026-03-25
  description: >-
    Official-style API reference for the public 511.org transit surface.


    Primary source documents for this reference snapshot:


    - [Transit spec PDF](/511/source/511-transit-spec.pdf)

    - [Overview spec PDF](/511/source/511-overview-spec.pdf)

    - [Data agreement PDF](/511/source/511-data-agreement.pdf)

    - [Pathways PDF](/511/source/511-pathways-stations.pdf)


    Implementation notes:


    - The public transit page and the transit PDF disagree on some
    query-parameter casing.

    - This reference uses the public page casing where the public API currently
    depends on it and calls out mismatches in endpoint descriptions.

    - The transit page currently documents a default limit of 60 requests per
    3600 seconds.
servers:
  - url: https://api.511.org
    description: Official 511.org API origin
security:
  - apiKeyQuery: []
tags:
  - name: Static NeTEx
    description: >-
      Static schedule and network structure endpoints backed by NeTEx content in
      a SIRI `ServiceDelivery` envelope.


      Covers transit spec sections 2.1 through 2.7 plus the Shapes endpoint
      described later in section 2.20.
  - name: Realtime SIRI
    description: >-
      Stop- and vehicle-level monitoring endpoints described in the transit PDF
      as SIRI services.


      This family covers StopTimetable, StopMonitoring, and VehicleMonitoring.
      The transit PDF also documents discontinued or future-looking SIRI
      services around announcements and timetable updates, which are not modeled
      as stable operations here.
  - name: GTFS & Bulk Feeds
    description: >-
      Bulk static GTFS and GTFS-Realtime feed download endpoints.


      The transit PDF also documents GTFS+ support files and historic regional
      feed behavior. Those details are supporting operational notes rather than
      request-by-request API fields.
paths:
  /transit/stops:
    get:
      tags:
        - Static NeTEx
      summary: Stops
      description: >-
        ScheduledStopPoint lookup for an operator. Based on transit spec section
        2.3 and JSON example B.1.3.
      parameters:
        - in: query
          name: format
          required: false
          description: Desired response format. JSON is the default when omitted.
          schema:
            type: string
            enum:
              - json
              - xml
            default: json
        - in: query
          name: accept_language
          required: false
          description: >-
            Optional language hint for NeTEx endpoints when multiple languages
            are available.
          schema:
            type: string
        - in: query
          name: operator_id
          required: true
          description: Operator or agency identifier.
          schema:
            type: string
        - in: query
          name: include_stop_areas
          required: false
          description: Include stop area groupings in stop responses.
          schema:
            type: boolean
        - in: query
          name: Direction_id
          required: false
          description: Direction filter as documented on the current transit page.
          schema:
            type: string
        - in: query
          name: line_id
          required: false
          description: Line or route identifier.
          schema:
            type: string
        - in: query
          name: pattern_id
          required: false
          description: Journey pattern identifier.
          schema:
            type: string
      responses:
        '200':
          description: Stops in JSON or XML.
          content:
            application/json:
              schema:
                type: object
              example:
                Siri:
                  ServiceDelivery:
                    DataObjectDelivery:
                      dataObjects:
                        ServiceFrame:
                          scheduledStopPoints:
                            ScheduledStopPoint:
                              - id: '18079'
                                Name: Mission St & 16th St
                                Location:
                                  Longitude: -122.4191
                                  Latitude: 37.7651
            application/xml:
              schema:
                type: string
              example: >-
                See the local transit spec PDF appendix example for Appendix
                A.1.3 / B.1.3.
        '401':
          $ref: '#/components/responses/Unauthorized'
        '404':
          $ref: '#/components/responses/NotFound'
        '500':
          $ref: '#/components/responses/InternalServerError'
components:
  responses:
    Unauthorized:
      description: Invalid API key.
      content:
        application/json:
          schema:
            type: object
            properties:
              message:
                type: string
    NotFound:
      description: Requested resource could not be located.
      content:
        application/json:
          schema:
            type: object
            properties:
              message:
                type: string
    InternalServerError:
      description: 511.org internal processing error.
      content:
        application/json:
          schema:
            type: object
            properties:
              message:
                type: string
  securitySchemes:
    apiKeyQuery:
      type: apiKey
      in: query
      name: api_key
      description: 511.org token query parameter.

````