# Apollo

> Connect Apollo with an API key and import call recordings and activity for SDR Call Intelligence.

Canonical URL: https://marcenta.ai/docs/connections/apollo
Markdown URL: https://marcenta.ai/site-md/docs/connections/apollo

Apollo supplies phone-call records, recording metadata, contacts, and outbound activity used by SDR Call Intelligence.

## Required Apollo access [#required-apollo-access]

Create an Apollo **Master API key** under an Apollo user and plan that can access the required phone-call and recording data. Marcenta imports calls through Apollo's call-search endpoint, which currently requires a Master API key. Provider availability, rate limits, and access can still depend on the Apollo subscription and the user's permissions.

Treat the key as a credential. Marcenta displays only whether a key is configured; it does not display the full saved key on the management page.

One Apollo key connection serves the active Marcenta workspace and can retrieve eligible calls across the associated Apollo team. Individual representatives do not connect separately.

## Create and verify the Apollo API key [#create-and-verify-the-apollo-api-key]

1. Sign in to the intended Apollo workspace as an administrator or a user whose Apollo permission profile permits API-key management.
2. Open **Settings → Integrations → API Keys**.
3. Select **Create new key**, enter a recognizable name such as `Marcenta SDR Call Intelligence`, and add a description identifying the owning team.
4. Enable **Set as master key**. Apollo's call-search endpoint requires a Master API key, so a scoped key will return a permission error for this connection.
5. Select **Create API key**, copy the value once, and paste it directly into Marcenta. Do not send it through email, chat, tickets, or screenshots.
6. In Apollo's developer dashboard, open **API Keys** to confirm the key exists and **Usage** to review endpoint rate limits and recent consumption.

If the user cannot create or manage keys, an Apollo administrator must either create the dedicated key or update the user's permission profile. Administrators can review assignments under **Settings → Users and teams → Users**, select the user, and choose **Edit permission profiles**. The key remains a high-privilege workspace credential even when the creating user is not an administrator, so rotate it when ownership changes or exposure is suspected.

See Apollo's guides to [creating and managing API keys](https://docs.apollo.io/docs/create-api-key), [call-search access requirements](https://docs.apollo.io/reference/search-for-calls), and [permission profiles](https://knowledge.apollo.io/hc/en-us/articles/4409154208269-Create-and-Assign-Permission-Profiles).

## Connect [#connect]

1. Generate a dedicated Apollo Master API key as described above.
2. Open **Connections → Apollo**.
3. Enter a recognizable connection name.
4. Paste the API key.
5. Choose an initial history window: 7, 15, 30, 60, or 90 days.
6. Complete setup and start the import.

Seven days is the default initial period and 90 days is the maximum initial selection. Start small when validating a new connection, then request additional history from the management page.

## Manage [#manage]

Open the Apollo connection to:

* review state and sync timestamps;
* rename the connection;
* sync recent activity;
* import a preset or custom historical period;
* replace the API key; or
* disconnect.

Rotate the key if the Apollo user changes role, the credential may have been exposed, or your security policy requires it. Confirm the replacement works before revoking the old key when continuity matters.

## Downstream call processing [#downstream-call-processing]

The connector import and SDR Call Intelligence are separate stages. An imported call can appear in **SDR Call Intelligence** while recording retrieval, transcript availability, analysis, or manager-review preparation is still pending.

Use the recording's displayed status to distinguish a source import issue from incomplete downstream processing.

## Troubleshooting [#troubleshooting]

| Symptom                         | What to check                                                                               |
| ------------------------------- | ------------------------------------------------------------------------------------------- |
| The key is rejected             | Generate a current key and confirm the Apollo user and plan permit API call access          |
| No calls appear                 | Check the initial period, Apollo call dates, recording availability, and latest sync result |
| Older calls are missing         | Run a historical import for the required period                                             |
| Calls appear without analysis   | Allow downstream processing to finish and inspect the recording status                      |
| A previously working sync fails | Confirm the key remains active and the Apollo user's access has not changed                 |

<Callout type="warn">
  Do not place Apollo API keys in documentation, support messages, screenshots, source code, or browser-visible configuration.
</Callout>