Check whether spans are actually arriving for a project
Reports the most recent span timestamp, a 24h span count, and any recorded ingest rejections for a project — the data zespan doctor’s Data flow check reads to tell “your integration is broken” apart from “this project hasn’t sent its first trace yet.”
lastSpanAt is bounded to a 90-day lookback (so the underlying ClickHouse query can prune partitions on large, long-lived projects). A project whose most recent span is older than that window reports lastSpanAt: null — identically to a project that has never sent anything. The two cases are not distinguishable from this response alone.
rejections is currently always an empty array: nothing in the ingest path persists rejection reasons yet, so the field is shipped honestly empty rather than backed by invented bookkeeping.
Authenticated with a dashboard session (browser cookie), not x-api-key — unlike every other endpoint on this page. It requires the dashboard:read permission on the project’s organization. A request carrying only a project API key does not satisfy this and receives 403.
Path Parameters
Project id.
Response
Ingest health for the project.
Timestamp of the most recent span in the last 90 days, or null if none — which covers both a project that has never sent a span and one whose last span is older than the 90-day lookback window.
214
Currently always empty — see the endpoint description.

