Signable
Connect Signable to Safeguard: what it provides, how to set it up, and the frameworks it provides evidence for.
Record your Signable 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 Signable:
- In Signable, click your account in the top right corner of the screen.
- From the dropdown, select Company Settings.
- Select the API & Webhooks tab.
- Click Add an API Key.
- Add a name for the key in the modal and click Save.
- Click Show to display the new API key, copy it and store it securely, then click the X icon to close.
Where to find the other values:
- API token / Personal access token: Company Settings › API & Webhooks after Add an API Key and Show.
Signable shows the secret only once, so copy it before you leave the page.
Signable's developer docs say the key is displayed only once and that all plans except Pay As You Go include API access; test keys are available separately from production keys. Signable issues no scoped or read-only key: the key authenticates as the company account. The API uses Basic HTTP authentication with the API key as the username. The developer docs label the controls 'Add API Key' and 'Show key' while the help centre uses 'Add an API Key' and 'Show'. The fetched pages did not state the API base URL, and Signable shows no separate account or workspace identifier for API use.
Source: help.signable.app, developers.signable.app, developers.signable.app, checked 2026-10-07.
-
On Compliance › Connectors, open Signable, 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
Signable 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