Apollo IO

Connect Apollo IO to collect business applications evidence with automated compliance tests, switched on per workspace.

Connect with an API token

1. In Apollo IO:

   1. In Apollo, go to Settings › Integrations and open API Keys.
   2. Click Create new key.
   3. Enter a name and a description, then turn on Set as master key (the Get a List of Users endpoint needs a master key or a key with the api/v1/users/search endpoint selected).
   4. Click Create API key and copy the key to a secure location.

   Source: docs.apollo.io, docs.apollo.io, checked 2026-10-07.

   The permissions Safeguard needs: master API key. Safeguard's compliance tests for Apollo IO need the credential on the API token tab: an OAuth connection cannot read everything they check.

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

   Field	What to enter
   API key	Required. Stored encrypted and never shown again.

3. Click Connect with token.

Connect with the MCP server

Choose MCP server: the address https://mcp.apollo.io/mcp is filled in. Sign in to Apollo IO when asked. It lets Griffin AI search Apollo IO; the compliance evidence comes from the API token connection.

Frameworks

Safeguard's automated tests read Apollo IO 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

• Business Applications 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