provider signals GET
/api/projects/{project_id}/signals/scout/runs/{run_id}/emissions/reports/ @utdk/posthog
/api/projects/{project_id}/signals/scout/runs/{run_id}/emissions/reports/ List the inbox reports a run's findings linked to
Best-effort reverse of the report -> signals link. For each finding the run emitted, resolve the inbox `SignalReport` (if any) its underlying signal grouped into by walking the deterministic `source_id` back through the signal store. `report` is null when the finding hasn't grouped into a report yet, was de-duplicated away, or its signal was deleted. Lets the scout UI surface which inbox report a finding contributed to — the reverse of the report's evidence list. 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.signalsScoutRunsEmissionReports()