Investigate Alert Across Scans
A 3-step recipe with Socket. We can help you get access.
Recipe · 3 steps
Investigate Alert Across Scans
with Socket
From the latest alert, list its associated full scans and read one scan's metadata.
- List the latest alerts and capture the first alert key to investigate.
- List the full scans that contain the chosen alert key within the requested day window.
- Read the metadata of the first associated full scan to identify the repository, branch, and commit that surfaced the alert.
What you'll need to have ready
- orgSlug: The slug of the organization.
- alertAction: Optional comma-separated alert actions to include (error, warn, monitor, ignore).
- range: Day offset window for associated scans (e.g. "-7d").
For your developer
Arazzo workflow socket-dev:investigate-alert-scans, 3 operations: alertsList → alertFullScans → getOrgFullScanMetadata. Specs on APIs.io.