---
title: "Stream Data"
method: GET
path: "/api/v1/dashboards/{dashboard_id}/data/stream"
tags: ["dashboards"]
---

# Stream Data

`GET /api/v1/dashboards/{dashboard_id}/data/stream`

Same results as ``/data``, delivered per widget as each one finishes.

A dashboard is only as fast as its slowest widget when the whole payload
has to be assembled first. Streaming lets the tiles that are ready render
immediately, which is most of them: widget cost on a real dashboard varies
by an order of magnitude.

Access is resolved once, up front — a viewer who may not see the dashboard
gets a 404 before the stream opens, not an error event inside it.

## Path parameters

- `dashboard_id` integer, required

## Query parameters

- `date_window` string, nullable — Narrow every widget to one period, overriding the dashboard's saved default.
- `widget_ids` integer[], nullable — Run only these widgets. The layout event then describes just the requested subset, so callers merge it into what they already hold rather than replacing their widget list.

## Headers

- `authorization` string, nullable
- `X-API-Key` string, nullable

## Response `200`

Successful Response

- unknown

## Other responses

- `422` — Validation Error

## Changes

- **2026-08-27** `db5ab8f1fcef` — 1 info
  - endpoint added

[Change history](https://skmtc.dev/ninjavan/apis/salesforce-sales-cloud-replacement/changes/api/v1/dashboards/:dashboard_id/data/stream/get.md)

---

[API](https://skmtc.dev/ninjavan/apis/salesforce-sales-cloud-replacement.md) · [All operations](https://skmtc.dev/ninjavan/apis/salesforce-sales-cloud-replacement/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/ninjavan/salesforce-sales-cloud-replacement/revisions/ce7abafbb050/schema)