Updating API Integrations

If you configure Socket through the REST API rather than the dashboard, these pages map the old Security Policy and Alert Triage endpoints onto the new ones:

• Security Policy API — the per-alert-type action map becomes a policy with a baseline plus explicit rules.
• Alert Triage API — pattern rules become policy rules; specific suppressions become alert resolutions.
• Translating Alert Triage Payloads — convert a POST /triage/alerts body into the new requests.
• Dry-Run Policy and Resolution Writes — ?dry_run=true on the new write endpoints: check the request without saving it. Use it for policy and rule writes before you confirm the migration.
• Alert Policy Migration Status — check where your organization is in the migration, and which configuration decides your alerts.

There is no time window during which you can write to both the old security-policy and triage endpoints and the new policy and rule endpoints, so it matters exactly how you change your scripts. Confirming the migration in the dashboard is the switch: policy and rule writes start working then, and the legacy writes stop. Do not wait until after cutover to start converting. Dry-run the new writes with ?dry_run=true before you confirm. The order:

1. Translate your POST /triage/alerts payloads so you know which ones become alert resolutions and which become policy rules.
2. POST the resolution bodies now. Those writes work before you migrate. Tokens need alert-resolution:create (and alert-resolution:list / :read / :delete to manage them).
3. Dry-run the translated policy and rule bodies. Those dry-runs work before you confirm the migration; a real POST still returns 409.
4. Confirm the migration in the dashboard. See Migrating to Policies.
5. POST the translated policy-rule bodies for real. Those writes only work after you confirm.
6. Stop writing to the legacy endpoints. Their GET responses stay 200, but they will not reflect changes you make in Policies after the cutover.

The migration window is 30 days from when migration is enabled for your organization. Your dashboard shows the exact date.

All requests use https://api.socket.dev/v0 with an organization API token, passed as a bearer token or as the user field in basic auth:

curl -u "$SOCKET_API_TOKEN:" https://api.socket.dev/v0/orgs/$ORG/alert-policies

When Writes Switch

Confirming the migration is the only switch. There is no in-between state where both write paths work.

Endpoint Mapping

Each legacy triage endpoint maps onto two replacements because the legacy triage table did two different jobs. Entries that changed the action for a class of packages become policy rules; entries that suppressed a specific finding become alert resolutions. Translating Alert Triage Payloads makes that split for you from a body you already have.

Policies also gained endpoints with no legacy equivalent, because policies did not exist as objects before: GET, PUT, and DELETE on /orgs/{org_slug}/alert-policies/{policy_id}, and GET, PUT, and DELETE on a single rule.

Token Scopes

Every alert-policy write and read endpoint requires a token with organization-wide repository access; tokens restricted to specific repositories receive 403. Translate is the exception on that group: repository-restricted tokens can call it, but posting the returned requests still needs an org-wide token. Alert resolutions are readable and writable by repository-restricted tokens within their granted repositories. See Resolve Alerts.

Full Reference

Complete request and response schemas for every endpoint are in the API reference:

• Policies — list, create, get, update, delete
• Policy rules — list, create, get, update, delete
• Alert resolutions — list, create, get, delete
• Translate — translate a triage payload
• Migration status — get the migration status
• Dry-run — the dry_run query parameter on every policy/rule write above, and on create a resolution. See Dry-Run Policy and Resolution Writes.

Related Pages

• Security Policy API
• Alert Triage API
• Translating Alert Triage Payloads
• Dry-Run Policy and Resolution Writes
• Alert Policy Migration Status
• Vigil Selectors
• Migrating to Policies