Safeguard Docs
Compliance ConnectorsSetup by categoryDigital Signature

SignWell

Connect SignWell to Safeguard: what it provides, how to set it up, and the frameworks it provides evidence for.

Record your SignWell connection as digital signature evidence. Automated collection is not available for this provider yet.

CategoryDigital Signature
Connect withAPI token
What a connection producesConnection record

Connect with an API token

  1. In SignWell:

    1. In SignWell, go to Settings › API and create your API token.
    2. Copy the key and paste it into Safeguard's API token / Personal access token field; SignWell expects it in the X-Api-Key header.

    Where to find the other values:

    • Base URL (optional): Not needed; not shown in a documented UI location.
    • Account / Org / Workspace (optional): Not shown in a documented UI location.

    SignWell's public documentation does not cover every step.

    SignWell's docs give only the Settings › API page; button labels, whether the key is shown once, and any read-only key option are not documented. The API key carries full account access. SignWell offers a test mode for development.

    Source: developers.signwell.com, checked 2026-10-07.

  2. On Compliance › Connectors, open SignWell, click Connect, choose API token and fill in:

    FieldWhat to enter
    API token / Personal access tokenRequired. Stored encrypted and never shown again.
    Base URL (optional)—
    Account / Org / Workspace (optional)—
  3. Click Connect with token.

Frameworks

SignWell 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.

FrameworkEvidenceControlsTests
SOC2AttestationCC6.2, CC6.31
ISO/IEC 27001AttestationA.5.181
HIPAA Security RuleAttestation164.308(a)(3)1
PCI DSSAttestation7.2.41
NIST CSF 2.0AttestationPR.AA-051

These tests are switched on per workspace by the Safeguard team.

On this page