provider signals GET
/api/projects/{project_id}/signals/scout/runs/{run_id}/emissions/ @utdk/posthog
/api/projects/{project_id}/signals/scout/runs/{run_id}/emissions/ List a run's emitted findings
Return the findings a `SignalScoutRun` emitted to the inbox, newest first — one row per emit with its `description` (the finding text as surfaced), `weight`, `confidence`, `severity`, and the deterministic `source_id` that joins back to the underlying signal. Lets a team and its agents see *what* a run surfaced without parsing `emitted_finding_ids` or scanning the signal store. Strictly team-scoped — a run UUID belonging to another team returns 404.
- project_id path required
- Project ID of the project you're trying to access. To find the ID of the project, make a call to /api/projects/.
- string
- run_id path required
- UUID of the `SignalScoutRun` bridge row.
- string
Try it
Authentication
Configure credentials for PostHog API
Code snippet
Updates live as you fill in the form above.
TypeScript
import posthog from '@utdk/posthog';
await posthog.signalsScoutRunsEmissions()