ContractSafe
Connect ContractSafe to Safeguard: what it provides, how to set it up, and the frameworks it provides evidence for.
Record your ContractSafe 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 ContractSafe:
- Log into your ContractSafe account.
- Select Settings, then Security & Integrations.
- Scroll down to Zapier at the bottom and copy the API Key/Org Token and API Secret.
Where to find the other values:
- Account / Org / Workspace (optional): Settings › Security & Integrations shows the API Key/Org Token next to the API Secret.
ContractSafe's public documentation does not cover every step.
ContractSafe confirms it has an open API, but the API documentation link could not be resolved, so it is unverified that the Zapier API Key/Org Token and API Secret are the credentials for its general API, or how they are sent. API and integrations are part of specific billing plans. ContractSafe credentials are shown on the settings page (not a one-time display); no read-only option is documented. The fetched page does not name a required role for the Settings page.
Source: contractsafe.com, contractsafe.com, checked 2026-10-07.
-
On Compliance › Connectors, open ContractSafe, 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
ContractSafe 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