> ## Documentation Index > Fetch the complete documentation index at: https://docs.zespan.com/llms.txt > Use this file to discover all available pages before exploring further. # 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`. ## OpenAPI ````yaml /api-reference/openapi.yaml get /v1/projects/{id}/ingest-health openapi: 3.1.0 info: title: Zespan Public API version: 1.0.0 description: > The Zespan Public API covers the endpoints that customers call directly or through the Zespan SDKs: trace ingestion (native and OpenTelemetry), prompt management, datasets and dataset runs, and the runtime guardrails check. All endpoints authenticate with a project API key sent in the `x-api-key` header. Create and manage API keys from the project settings in the Zespan dashboard. servers: - url: https://api.zespan.com description: Zespan production API security: - ApiKeyAuth: [] tags: - name: Ingestion description: Send traces and events to Zespan. - name: OpenTelemetry description: OTLP-compatible ingestion endpoints. - name: Prompts description: Manage versioned prompts and their labels, tags, and folders. - name: Datasets description: Read datasets and manage dataset runs used for experiments and scoring. - name: Guardrails description: Runtime guardrail evaluation. - name: SDK / CLI support description: > Small support endpoints consumed by the SDKs and @zespan/cli rather than called directly by application code. - name: Blast Radius description: > The prompt/agent/model/policy/evaluator/alert dependency graph backing the pre-release impact check and the evaluator-delete gate in the dashboard. Session-authenticated (dashboard cookie), not `x-api-key`. - name: Outcomes description: > Report business outcomes (a deflected ticket, an avoided refund, an SLA met) attributed to a trace, and read them back summarized by agent or model, joined to real trace cost. Backs the Value dashboard page. The ingest endpoint is `x-api-key`-authenticated like the rest of ingestion; the two read endpoints are session-authenticated (dashboard cookie) like Blast Radius. - name: Compliance description: > Generate audit-ready evidence documents (a per-agent Compliance Card, or SOC 2 control evidence) from recorded platform data, and re-verify a generated document's citations against live data. Session-authenticated (dashboard cookie), not `x-api-key`, gated by `compliance:read` / `compliance:generate` permissions and the Pro plan or above (the framework listing is the one exception — no project scope and no plan gate, since a customer deciding whether to upgrade needs to see what they'd get). - name: Models description: > Per-model usage, cost, latency, and error-rate rollups for a project, including the lifecycle overlay described under the Model Lifecycle tag. Session-authenticated (dashboard cookie), not `x-api-key`, gated by `dashboard:read`. - name: Model Lifecycle description: > Findings from the daily model deprecation scan, which matches models a project actually calls against a curated, bundled catalogue of provider-announced deprecation and retirement dates. Every figure on a finding (call volume, cost, affected agents/prompts, cost comparison against a named successor) is measured from real trace data — there is no quality-delta or regression-comparison endpoint, because nothing in this API invokes a model on the caller's behalf. Session-authenticated (dashboard cookie), not `x-api-key`: reading findings and the catalogue requires `dashboard:read`, dismissing a finding requires `alerts:manage`. paths: /v1/projects/{id}/ingest-health: get: tags: - SDK / CLI support summary: Check whether spans are actually arriving for a project description: > 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`. operationId: getIngestHealth parameters: - name: id in: path required: true schema: type: string format: uuid description: Project id. responses: '200': description: Ingest health for the project. content: application/json: schema: $ref: '#/components/schemas/IngestHealthResponse' '403': description: >- Not authenticated with a dashboard session, or lacks `dashboard:read`. content: application/json: schema: $ref: '#/components/schemas/Error' '404': $ref: '#/components/responses/NotFound' security: [] components: schemas: IngestHealthResponse: type: object properties: lastSpanAt: type: string format: date-time nullable: true description: > 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. spanCount24h: type: integer example: 214 rejections: type: array items: $ref: '#/components/schemas/IngestHealthRejection' description: Currently always empty — see the endpoint description. required: - lastSpanAt - spanCount24h - rejections Error: type: object properties: error: type: string description: Human-readable error message. example: Unauthorized code: type: string description: Machine-readable error code, when present. example: rate_limit_exceeded required: - error IngestHealthRejection: type: object properties: reason: type: string example: quota_exceeded count: type: integer example: 12 lastAt: type: string format: date-time responses: NotFound: description: Resource not found. content: application/json: schema: $ref: '#/components/schemas/Error' securitySchemes: ApiKeyAuth: type: apiKey in: header name: x-api-key description: >- Project API key. Manage keys in the Zespan dashboard under project settings. ````