signals

List emitted findings for many runs at once

Batched form of the per-run emissions endpoint: return the findings every requested SignalScoutRun emitted, flattened newest-first, in a single request. Each row carries its run_id, so the caller can regroup by run. The findings UI uses this to load the whole recent window in one round-trip instead of one request per run. Strictly team-scoped — run ids belonging to another team contribute no rows (no per-run 404; one stale id never fails the batch).

post/api/projects/{project_id}/signals/scout/runs/emissions/batch/

Request

  • Base URL: https://us.posthog.com
  • URL: https://us.posthog.com/api/projects/{project_id}/signals/scout/runs/emissions/batch/
  • Auth: one of:
    • HTTP bearer
    • HTTP bearer

Path parameters

project_idstring required

Project ID of the project you're trying to access. To find the ID of the project, make a call to /api/projects/.

Request body

run_idsstring[] required

UUIDs of the SignalScoutRun rows to resolve in one batch. Run ids belonging to another team are silently ignored (they contribute no rows) rather than failing the whole request. Capped at 200 ids per call.

Response

Findings emitted across all requested runs, newest first.

idstring uuid required
run_idstring required

UUID of the SignalScoutRun that emitted this finding.

finding_idstring required

Stable id the finding was emitted under; matches an entry in the run's emitted_finding_ids.

descriptionstring required

The emitted finding prose — the signal's description as surfaced to the inbox.

tagsstring[] required

Slug tags the scout attached to this finding (lowercase kebab-case, e.g. cost-spike). Empty list when the run set none.

source_idstring required

Deterministic run:<run_id>:finding:<finding_id> — the join key into the underlying signal store.

emitted_atstring date-time required

ISO-8601 timestamp the finding was emitted.

Changes

No recorded changes to this operation across all 1 revision of this API.