Safeguard Docs
Compliance ConnectorsSetup by categoryDigital Signature

GetAccept

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

Record your GetAccept 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 GetAccept:

    1. GetAccept does not issue API keys in the app. Contact your GetAccept representative or Tech Support to provision API credentials (a token, or OAuth 2.0 configured by GetAccept Tech Support) and to confirm API access is included in your plan.
    2. Paste the token GetAccept provides into Safeguard.

    GetAccept issues this credential through its API or its support team, not through its admin screens.

    GetAccept says older guidance about an "Integrations > API key" settings page is incorrect; credentials are provisioned by GetAccept. Ask them for read-only scope if available; plan, rate and scope considerations are confirmed by your representative.

    Source: help.getaccept.com, help.getaccept.com, checked 2026-10-07.

  2. On Compliance › Connectors, open GetAccept, 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

GetAccept 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