HyperComply
Connect HyperComply to Safeguard: what it provides, how to set it up, and the frameworks it provides evidence for.
Record your HyperComply connection as vendor procurement evidence. Automated collection is not available for this provider yet.
| Category | Vendor Procurement |
| Connect with | API token |
| What a connection produces | Connection record |
Connect with an API token
-
In HyperComply:
- Obtain a HyperComply API client ID and client secret for your organization (the public API reference does not say where in the HyperComply app they are issued).
- Exchange them for an access token: POST to https://api.hypercomply.com/oauth_api/token with a JSON body containing client_id, client_secret and grant_type set to client_credentials (the only supported grant).
- The response returns access_token and expires_at; send the access token on API calls.
Where to find the other values:
- Base URL (optional): HyperComply's Public API is served under https://api.hypercomply.com/oauth_api (API reference at https://api.hypercomply.com/oauth_api/docs).
HyperComply's public documentation does not cover every step.
HyperComply (now part of SecurityScorecard) publishes an OpenAPI spec, 'HyperComply Public API' v1.1.0, that uses OAuth 2.0 client credentials with tokenUrl /oauth_api/token and no scopes, so no read-only scope is documented. Neither the spec nor the HyperComply articles on SecurityScorecard's help center (read through the help center's article API; HTML returned 403) say where in the HyperComply app the client ID and secret are issued. Searches of that help center for 'HyperComply API token', 'API key' and 'client secret' returned only integration articles. The support article describes API access as a 'Secure Token' integration for Trust Page provisioning.
Source: api.hypercomply.com, api.hypercomply.com, support.securityscorecard.com, checked 2026-10-07.
-
On Compliance › Connectors, open HyperComply, 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
No automated compliance test reads HyperComply yet, so no framework lists it. How connectors provide evidence for frameworks: Frameworks and connectors.
Related
- Vendor Procurement 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