LinkSquares
Connect LinkSquares to Safeguard: what it provides, how to set it up, and the frameworks it provides evidence for.
Record your LinkSquares 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 LinkSquares:
- Sign in to the LinkSquares web app as the user who will own the key. LinkSquares recommends a service account (for example linksquares_api@companydomain.com) rather than a person's account, and that user must be an Analyze or Finalize Administrator; the IT Administrator role cannot manage API keys.
- Go to Settings from the app selector.
- Select API Keys.
- Press GENERATE API KEY, then store the key in a password manager; anyone holding it has the equivalent of access to your agreements.
Where to find the other values:
- API token / Personal access token: Settings › API Keys in the LinkSquares web app, after you press GENERATE API KEY. It is sent in the x-api-key header.
- Base URL (optional): https://api.linksquares.com (LinkSquares' example call is https://api.linksquares.com/api/analyze/v1/agreements).
- Account / Org / Workspace (optional): Not needed: each LinkSquares API key is tied to one user and company. Leave blank.
Read through the help center's public Zendesk article API because the HTML page returns 403 to non-browser requests. LinkSquares API keys work for both Analyze and Finalize. LinkSquares documents no read-only key; access follows the owning user, which must be an Analyze or Finalize Administrator. Keys can be disabled with the Enabled toggle (takes up to five minutes) or deleted with the trash icon. The article does not say whether the key stays visible after it is generated.
Source: help.linksquares.com, help.linksquares.com, checked 2026-10-07.
-
On Compliance › Connectors, open LinkSquares, 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
LinkSquares 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