> ## Documentation Index
> Fetch the complete documentation index at: https://docs.mireye.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# GET /v1/runs/{run_id}/events

> Watch a batch run's progress as Server-Sent Events instead of polling.

A convenience over polling [`GET /v1/runs/{run_id}`](/api-reference/runs).
Emits a `status` frame on every state or progress change, then one terminal
`final` frame carrying the complete run body.

<Info>
  The poll endpoint remains the source of truth. If the stream drops, fall back
  to polling — do not treat a dropped connection as a failed run.
</Info>

```bash theme={null}
curl -N -s "https://api.mireye.com/v1/runs/$RUN_ID/events" \
  -H "Authorization: Bearer $MIREYE_API_TOKEN" \
  -H 'accept: text/event-stream'
```

```text theme={null}
event: status
data: {"status":"running","completed":128,"total":1000}

event: status
data: {"status":"running","completed":512,"total":1000}

event: final
data: {"run_id":"...","status":"succeeded","result":{...}}
```

Useful when a screen is long enough that a human wants a progress bar, or
when an agent should start reading partial results rather than blocking on
the whole batch. For the artifact once it finishes, see
[run artifacts](/api-reference/run-artifacts).


## OpenAPI

````yaml GET /v1/runs/{run_id}/events
openapi: 3.1.0
info:
  title: Mireye Earth
  description: >-
    Provenance-tagged geospatial data for US coordinates. POST /v1/fetch for
    deterministic field values (POST /v1/fetch/batch for up to 25 locations at
    once); POST /v1/ask for natural-language Q&A; GET /v1/meta/fields for the
    catalog.
  version: 0.16.0
servers: []
security: []
paths:
  /v1/runs/{run_id}/events:
    get:
      summary: Stream a run's progress (SSE)
      description: >-
        Server-sent events: a `status` frame on every state/progress change and
        a terminal `final` frame carrying the full run body. A convenience over
        polling — the poll endpoint is the source of truth.
      operationId: run_events_v1_runs__run_id__events_get
      parameters:
        - name: run_id
          in: path
          required: true
          schema:
            type: string
            title: Run Id
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema: {}
        '422':
          description: Validation Error
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/HTTPValidationError'
components:
  schemas:
    HTTPValidationError:
      properties:
        detail:
          items:
            $ref: '#/components/schemas/ValidationError'
          type: array
          title: Detail
      type: object
      title: HTTPValidationError
    ValidationError:
      properties:
        loc:
          items:
            anyOf:
              - type: string
              - type: integer
          type: array
          title: Location
        msg:
          type: string
          title: Message
        type:
          type: string
          title: Error Type
        input:
          title: Input
        ctx:
          type: object
          title: Context
      type: object
      required:
        - loc
        - msg
        - type
      title: ValidationError

````