Loopio

Connect Loopio to collect vendor procurement evidence with automated compliance tests, switched on per workspace.

Connect with an API token

1. In Loopio:

   1. Sign in to Loopio as an Admin (only Loopio Admins can create a Client) and open the Admin/Integrations page.
   2. Scroll to the For Developers section and click Add an App.
   3. Name the app and select only the scopes user:read and role:read. Scopes cannot be changed after the app is created; to change them you must delete the app and create a new one.
   4. Save. Loopio shows the Client's ID and secret; copy both now, because the secret is only visible while you remain on this page.
   5. If you paste an access token instead of the client ID and secret: request one with the client_credentials grant by POSTing grant_type=client_credentials, scope=user:read role:read, client_id and client_secret to https://api.loopio.com/oauth2/access_token. The token expires after 3600 seconds.

   Where to find the other values:

   • Client ID (optional): Shown with the secret right after you save the app under Admin/Integrations › For Developers › Add an App.
   • Client secret (optional): Shown once on the same page after saving the app; it is only visible while you remain on that page.
   • Access token: Returned in the access_token field of the response from POST https://api.loopio.com/oauth2/access_token (client_credentials grant).
   • Region (optional): Loopio has North America (api.loopio.com) and Europe (api.eu.loopio.com) datacenters; credentials from one do not work in the other. Loopio's docs say the European API is not yet accessible, so use api.loopio.com. int01 testing instances use api.int01.loopio.com with their own credentials.

   Loopio shows the secret only once, so copy it before you leave the page.

   Read from Loopio's official Stoplight developer portal (developer.loopio.com) through its public node API, since the portal renders client-side. user:read and role:read both appear in Loopio's OpenAPI definition. Access tokens last one hour (expires_in 3600).

   Source: loopio.stoplight.io, loopio.stoplight.io, loopio.stoplight.io, checked 2026-10-07.

   The permissions Safeguard needs: user:read, role:read.

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

   Field	What to enter
   Access token	Optional. Stored encrypted and never shown again.
   Region (optional)	—

   Or, instead: Client ID (optional), Client secret (optional).

3. Click Connect with token.

Frameworks

Safeguard's automated tests read Loopio and map to the controls below. When a test passes, the result is evidence toward each control it maps to, in every framework listed. It is evidence toward a control, not proof that the control is met on its own.

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