Probely

Connect Probely to collect vulnerability scanning evidence with automated compliance tests, switched on per workspace.

Connect with an API token

1. In Probely:

   1. Sign in to the Snyk API & Web app (formerly Probely).
   2. Generate an API Key and treat it like a password: what it can access depends on the role associated with the key. Snyk's Help Center article 'How to generate an API Key' has the exact clicks.

   Probely's public documentation does not cover every step.

   Probely is now Snyk API & Web. Its developer docs say an API key's access depends on the role associated with the key, and the key is sent as 'Authorization: JWT <key>' to https://api.probely.com. The Help Center article with the exact menu path (help.probely.com) returned 403 to automated fetches, so the click path and role names could not be sourced.

   Source: developers.probely.com, developers.probely.com, checked 2026-10-07.

   The permissions Safeguard needs: read-only role.

2. On Compliance › Connectors, open Probely, click Connect, choose API token and fill in:

   Field	What to enter
   API key	Required. Stored encrypted and never shown again.

3. Click Connect with token.

Frameworks

Safeguard's automated tests read Probely and map to the controls below. When a test passes, the result is evidence toward each control it maps to, in every framework listed. It is evidence toward a control, not proof that the control is met on its own.

These tests are switched on per workspace by the Safeguard team.

Related

• Vulnerability Scanning connectors
• Compliance connectors: how connecting works, card statuses and multiple accounts
• Connector setup reference: every connector in one table
• Frameworks and connectors: how connectors provide evidence for frameworks