Blink Ops
Connect Blink Ops to Safeguard: what it provides, how to set it up, and the frameworks it provides evidence for.
Record your Blink Ops connection as security automation evidence. Automated collection is not available for this provider yet.
| Category | Security Automation |
| Connect with | API token |
| What a connection produces | Connection record |
Connect with an API token
-
In Blink Ops:
- In Blink, open the API Keys settings page.
- Select the New API Key button in the top-right corner.
- Give the key a name, an optional description, and choose when it expires (after 30 days, 90 days or never).
- Click the Create button in the bottom-right corner. The key is added to the table; copy the value from the Key column.
Where to find the other values:
- Base URL (optional): The Blink REST API is served from app.blinkops.com.
Blink Ops's public documentation does not cover every step.
API keys are personal and carry the creating user's access; Blink documents no read-only scope. Maximum five keys, and one must always exist. The menu path to the API Keys page is not given in the docs. No workspace identifier is documented. The docs do not say whether the key value can be viewed again after creation.
Source: docs.blinkops.com, docs.blinkops.com, checked 2026-10-07.
-
On Compliance › Connectors, open Blink Ops, click Connect, choose API token and fill in:
Field What to enter API token / Personal access token Required. Stored encrypted and never shown again. Base URL (optional) — Account / Org / Workspace (optional) — -
Click Connect with token.
Frameworks
No automated compliance test reads Blink Ops yet, so no framework lists it. How connectors provide evidence for frameworks: Frameworks and connectors.
Related
- Security Automation 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