Eversign
Connect Eversign to Safeguard: what it provides, how to set it up, and the frameworks it provides evidence for.
Record your Eversign connection as digital signature evidence. Automated collection is not available for this provider yet.
| Category | Digital Signature |
| Connect with | API token |
| What a connection produces | Connection record |
Connect with an API token
-
In Eversign:
- Log in to Eversign (now Xodo Sign) and open the business you want to connect.
- Open the top left dropdown menu and select Developer.
- Copy the API access key shown there (each account has one unique access key).
Where to find the other values:
- Base URL (optional): The API base URL is
https://api.eversign.com(HTTPS only). - Account / Org / Workspace (optional): The Business ID, shown on the same Developer page (top left dropdown menu) after logging in to that business; it is sent as
business_id.
Eversign is now Xodo Sign; the docs still use api.eversign.com. The access key is a single account-wide key passed as the access_key query parameter; there is no read-only or scoped key. The key is displayed on the Developer page (not a one-time display).
Source: eversign.com, checked 2026-10-07.
-
On Compliance › Connectors, open Eversign, 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
Eversign 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 |
These tests are switched on per workspace by the Safeguard team.
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