Apollo.io
Connect Apollo.io as an access review source using a master API key so Probo can list your account's team members and permission profiles.
Probo reads your Apollo.io account’s team members through the Apollo REST API so you can review who has access. Probo reviews Apollo teammates (account seats), not prospect or contact records.
Prerequisites
Section titled “Prerequisites”- Probo organization administrator access
- The Apollo account admin role, or a permission profile that grants API key creation
- A master API key (created with the Set as master key toggle), since Probo reads the master-key-only Get a List of Users endpoint
Collected Fields
Section titled “Collected Fields”| Probo field | Apollo.io field | Notes |
|---|---|---|
| Name | name | Falls back to first and last name, then the email |
email | ||
| Role | role | The Apollo permission-profile name for the user |
| Admin | role | Flagged as an administrator when the role name equals Admin |
| Status | Not supported | |
| MFA | Not supported | |
| Last login | Not supported | |
| External ID | id | Stable identifier used to track the account across reviews |
| Created at | Not supported |
Step 1: Create an API Key
Section titled “Step 1: Create an API Key”
- In Apollo (signed in as an account admin), go to Settings > Integrations > API Keys > Create new key.
- Name the key (e.g.
Probo Access Review) and toggle Set as master key so it can reach the Get a List of Users endpoint that Probo reads. - Save the key immediately and store it securely. Apollo may not show it again.
Step 2: Connect in Probo
Section titled “Step 2: Connect in Probo”- In Probo, go to Access Review > Connections.
- Find Apollo.io, click API Key, paste the key, and click Connect.
Probo names the source Apollo.io (the fixed provider name), since Apollo exposes no stable account-name endpoint. Probo pulls the account’s members into your campaigns.
Troubleshooting
Section titled “Troubleshooting”- Key rejected. Confirm it’s a master key created with Set as master key enabled. A non-master, endpoint-scoped key is rejected because the Get a List of Users endpoint is master-key-only.
- No members appear. The key must be created by an account admin (or a permission profile that grants API key creation) and belong to the Apollo account you’re reviewing.