> For the complete documentation index, see [llms.txt](https://docs.pandium.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pandium.com/connectors/connectors-101/apollo.io.md).

# Apollo.io

Set up the Apollo.io connector in Pandium using your scoped or master API key so tenants can authenticate securely and sync prospecting and sales engagement data.

## **Connector Overview**

<figure><img src="https://lh7-rt.googleusercontent.com/docsz/AD_4nXek3Tqst1fjYeDfhtnXC6gvMj7-uFs-cD75p4FMpm5sOY_Zzt4crV385WV2_4gF-XGZ-Yp0WNOoMR--spEOXAcfx2eRGC_o-hhzBhD9y2xHqvms5R7wuZjpUubYUsQ-sDDwotu-cg?key=XIy8122ZNqmu67sUe4Q2WNF3" alt="" width="375"><figcaption></figcaption></figure>

Apollo.io is a sales engagement platform that combines prospecting, data enrichment, and outreach tools. It empowers businesses to find leads, connect with prospects, and optimize workflows to drive sales and growth effectively.

## **Authentication Type**

Basic

## **Webhook Supported**

No

## **Secrets**

* PAN\_SEC\_APOLLO\_IO\_API\_KEY

## **API Client Supported**

Yes. You can read more about the capabilities of the Integration Development Kit [here](broken://spaces/-MfdKgN0cGTpmF3-1gDd/pages/sJfQYq4MK2Bke6lrfErK).

## **Requirements for Provisioning**

No provisioning is required for this connector.

## **How to Connect Your Integration**

Upon successfully creating a tenant, you will use the following information to connect to Apollo:

* API Key

To obtain the information required for setting up, perform the following steps:

1. Launch Apollo and click Settings > [Integrations](https://app.apollo.io/#/settings/integrations).
2. Find the API option and click Connect.\
   ![alt text](https://lh7-rt.googleusercontent.com/docsz/AD_4nXcId0Y1EGk6W5dhrmZEMqkKQUh3uBbSQl1ZsYH7usZrflHYd1RloTNdL9R9ZECxd_qblPuBZad1-MVfzrE8Zllp3P-dlUBO9F--Wru0VOaUyZHdz2lzuGHvktiqkjzCD2SVactJig?key=XIy8122ZNqmu67sUe4Q2WNF3)
3. Click API keys to view or create new API keys. Then, click Create new key.\
   ![alt text](https://lh7-rt.googleusercontent.com/docsz/AD_4nXdOfZx9cRtgcYJNeqqGMlzO-rcFPI0JLV8yU4gV-b7wvNFsPRAP0zIFb57YwVmFLOAFA-rZ1LYp_iHxIBmNwCYhYs9p-U8aeyjI0PqcCZPMGyziZ3vHPWOrljVnsZfTwifJ903M2w?key=XIy8122ZNqmu67sUe4Q2WNF3)
4. Name your API Key and add a description. To scope your key appropriately, click the checkbox for each Apollo API endpoint you need to access.\
   ![alt text](https://lh7-rt.googleusercontent.com/docsz/AD_4nXcILqybI-xI37FbUcE7P7izqirIqoze7Um0fXxAMVtAiYUHHvqEsGNjzJVooORg396TV3KtiWseA64cHGBtpUOSpjxhULGcGt2qZilcL5ziK4aPSbvB80K9bKjCC7NmotbctNomIw?key=XIy8122ZNqmu67sUe4Q2WNF3)
5. To access all endpoints that are available with your Apollo plan, set your key to be a master key by toggling on the Set as master key slider. Certain endpoints such as [Get a List of Users](https://docs.apollo.io/docs/get-a-list-of-users) are only accessible when using a master API key.\
   ![alt text](https://lh7-rt.googleusercontent.com/docsz/AD_4nXcoUk1ezzcTLqAGbmviLasRKrT4ICedksR9hTDt4E3ulctcBPSeWLuzFtxoXOxb7Gx4s0_CgHA_vwIniBdTZWZp4OxhvneZtj-rHlhZGSyg8DOXovpVgTaIURcl9FKRUL06oHRY?key=XIy8122ZNqmu67sUe4Q2WNF3)
6. Click Create API key.

## **API Resources**

For more information on how to utilize the Apollo.io API, feel free to reference the following [documentation](https://docs.apollo.io/?shell#introduction).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.pandium.com/connectors/connectors-101/apollo.io.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
