Zluri
Connect Zluri to Safeguard: what it provides, how to set it up, and the frameworks it provides evidence for.
Record your Zluri connection as user access review evidence. Automated collection is not available for this provider yet.
| Category | User Access Review |
| Connect with | API token |
| What a connection produces | Connection record |
Connect with an API token
-
In Zluri:
- Request a secure API key from Zluri Support.
- Paste the key into Safeguard; Zluri's API expects it in the api-key header.
Where to find the other values:
- Base URL (optional): Zluri documents the API base URL as https://api-ext.zluri.com (v2 endpoints under https://api-ext.zluri.com/ext/v2/).
Zluri issues this credential through its API or its support team, not through its admin screens.
Zluri's public API docs say to request the key from Zluri Support and document no UI path, scopes or read-only option. Ask Support for a key limited to read access if they offer one.
Source: developers.zluri.com, developers.zluri.com, checked 2026-10-07.
-
On Compliance › Connectors, open Zluri, 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 Zluri yet, so no framework lists it. How connectors provide evidence for frameworks: Frameworks and connectors.
Related
- User Access Review 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