> ## Documentation Index
> Fetch the complete documentation index at: /docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Prospect and Enrich Leads in Apollo.io With Agents

> Let agents search and enrich people and companies in Apollo.io and manage contacts, deals, and sequences. Your API key stays hidden from the agent.

## Overview

Buckle 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.

## What you will set up

* An Apollo.io API key, limited to the endpoints your agents need
* Automatic key injection on requests to `api.apollo.io`
* Per-agent, per-tool access, such as approval before sequence enrollment

## 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](https://docs.apollo.io/docs/create-api-key).

**2. Connect in Buckle**

Open **Settings** > **Apps** > **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.

![Buckle 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.](https://mintcdn.com/onecli-17d3f772/hJP3XqgFsBDnXHKy/images/integrations/apollo-io/buckle-connect-apollo-io.png?fit=max\&auto=format\&n=hJP3XqgFsBDnXHKy\&q=85\&s=18fbae4784cef9bf034d186510dcb26f)

The Apollo.io connect dialog in Buckle.

## What agents can do

| Area | Description |
| - | - |
| **People search** | Find prospects by title, company, location, and other filters |
| **Company search** | Find organizations by name, domain, industry, and size |
| **Enrichment** | Enrich people and companies (uses Apollo credits) |
| **Contacts** | Search, view, create, and update contacts |
| **Accounts** | Search, view, create, and update accounts |
| **Deals** | List, view, create, and update deals |
| **Tasks** | Search, create, and update tasks |
| **Sequences** | Search sequences and add contacts to them |

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

## Quick example

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

```bash theme={null}
# Search for people at a company (filters are query parameters)
curl -sg -X POST "https://api.apollo.io/api/v1/mixed_people/api_search?q_organization_domains_list[]=example.com&per_page=10"

# Enrich a person by email
curl -s -X POST "https://api.apollo.io/api/v1/people/match?email=jane@example.com"
```

## Disconnecting

* In Buckle, open **Settings** > **Apps** > **Apollo.io** and remove the connection.
* Then delete the key in Apollo under **Settings** > **Integrations** > **API keys**.

## Controlling access

Access is per agent: [grant](/docs/guides/agent-access.md) 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](/docs/guides/rules.md) add guardrails on top, like rate limits. Everything is checked before credential injection, so a blocked request never reaches Apollo.

## FAQ

> [accordion] How do I rotate my Apollo API key?
>
> Create a new key in Apollo under **Settings** > **Integrations** > **API keys**, then paste it into **Settings** > **Apps** > **Apollo.io**. Agents pick up the new key automatically. Then delete the old key in Apollo.

> [accordion] How do I keep the Apollo key out of the agent's context?
>
> Store it in Buckle. The gateway adds it at the proxy, so agents call the API with no auth header and never see the key. See [How it works](/docs/how-it-works.md).

> [accordion] Why does an endpoint return a permission error?
>
> The connection can only reach the endpoints you selected when creating the key. Create a key that includes that endpoint, or turn on **Set as master key**.

> [accordion] Can I stop agents from spending enrichment credits freely?
>
> Yes. Enrichment uses Apollo credits, so set it to need approval when you [grant](/docs/guides/agent-access.md) the connection, or add a rate limit with [rules](/docs/guides/rules.md).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.