Responsive
Connect Responsive to Safeguard: what it provides, how to set it up, and the frameworks it provides evidence for.
Record your Responsive 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 Responsive:
- Sign in to Responsive with the user or service user the key should be issued from. Responsive API keys inherit the permissions of the user or service user they are issued from, so use one with permissions only for the resources Safeguard will read.
Where to find the other values:
- Base URL (optional): The base URL for your Responsive region; Responsive's developer portal lists it as a prerequisite but the region-specific URL was not readable on the fetched pages.
Responsive's public documentation does not cover every step.
Responsive (formerly RFPIO) API keys inherit the permissions, and audit identity, of the user or service user they are issued from. Verification (2026-10-07): both developer.responsive.io articles render their body with JavaScript and could not be read; only the portal's embedded overview text was readable. The menu path to generate a token, the button label, whether the key is shown once, and the default base URL were removed because no fetched source states them. Re-check the token path in the article in a browser before publishing.
Source: developer.responsive.io, developer.responsive.io, checked 2026-10-07.
-
On Compliance › Connectors, open Responsive, 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
Responsive 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
- 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