Juro
Connect Juro to Safeguard: what it provides, how to set it up, and the frameworks it provides evidence for.
Record your Juro connection as digital signature evidence.
| Category | Digital Signature |
| Connect with | API token |
| What a connection produces | Connection record |
Connect with an API token
-
In Juro:
- In Juro, open the API page in your account settings.
- Click Generate API key and copy the key.
Where to find the other values:
- Base URL (optional): Production is
https://api.juro.com; the sandbox ishttps://api-sandbox.juro.io.
The key is sent as the x-api-key header. Without the API & Webhooks add-on on your Juro order form the quota is 100 requests per month; with it, 20,000 per day. Juro documents no read-only key. If calls return Unauthorized, deactivate and reactivate the key in Juro > Settings > Integrations > API. The docs do not say whether the key is shown only once.
Source: api-docs.juro.com, checked 2026-10-07.
-
On Compliance › Connectors, open Juro, 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
Juro publishes no API for what these tests check, so its evidence is an attestation: connect it to record the connection, then attest the result. An accepted attestation counts toward each control below.
| Framework | Evidence | Controls | Tests |
|---|---|---|---|
| SOC2 | Attestation | CC6.2, CC6.3 | 1 |
| ISO/IEC 27001 | Attestation | A.5.18 | 1 |
| HIPAA Security Rule | Attestation | 164.308(a)(3) | 1 |
| PCI DSS | Attestation | 7.2.4 | 1 |
| NIST CSF 2.0 | Attestation | PR.AA-05 | 1 |
Related
- Digital Signature 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