Skip to main content

Overview

OneCLI connects AI agents to Apollo.io with an API key. Agents can search Apollo’s people and company database, enrich records, and manage contacts, accounts, deals, tasks, and sequences. The gateway injects the key into requests to api.apollo.io, so your agent never sees it.

Setup

1

Create an API key in Apollo

In Apollo, go to Settings > Integrations > API keys and create a key. Select only the endpoints your agents need, or turn on Set as master key for full access. See Apollo’s guide: Create API keys.
2

Connect in OneCLI

Open Connections > Apollo.io, paste your key, and click Connect Apollo.io. Under Advanced you can add an optional connection label to tell multiple Apollo accounts apart.
OneCLI connect dialog for Apollo.io, showing the required API key field, a link on how to create an Apollo API key, an Advanced section with an optional connection label, and the Connect Apollo.io button.

The Apollo.io connect dialog in OneCLI.

What agents can do

What a connection can actually reach follows the API key: endpoints you left out when creating the key return permission errors, regardless of what OneCLI allows.

Quick example

An agent calling the Apollo API through the gateway. No auth header is needed, the gateway adds it:

Disconnecting

  • In OneCLI, open Connections > Apollo.io and remove the connection.
  • Then delete the key in Apollo under Settings > Integrations > API keys.

Controlling access

Access is per agent: grant the connection to each agent that needs it, choosing per tool what runs freely, what needs human approval, and what stays blocked. For example, allow people search but require approval before an agent enrolls contacts in a sequence. Organization rules add guardrails on top, like rate limits. Everything is checked before credential injection, so a blocked request never reaches Apollo.