Apollo

Overview
How to connect
Automated checks
Useful links

Connect Apollo with a master API key to sync team users and run access reviews. Read-only.

Read-only access. DSALTA only reads data from this integration. It never creates, modifies, or deletes anything in your environment, and every remediation step is performed by your team directly in the third-party product.

DSALTA collects this integration’s data when you connect it — you can refresh it at any time with Sync from integrations on the Integrations page. The compliance checks below re-run once a day at 02:00 America/New_York.

What DSALTA reads

DSALTA reads your Apollo team roster — first and last name, email address, creation date and active status — which appears on your Access page. That is the whole sync: contacts, accounts, deals, sequences and email activity are never read. Listing team users requires an Apollo master API key.It calls this Apollo endpoint:

/v1/users/search

Every request is a read. DSALTA has no code path that creates, modifies, or deletes anything in your Apollo environment.

Troubleshooting

The connection is rejected, or nothing appears on the Access page

Almost always the key is not a master key. Apollo scopes API keys per endpoint by default, and the user-list endpoint returns 403 for a scoped key even when its Users checkbox is ticked. Create a new key with Set as master key toggled on, then disconnect and connect again.

Every Apollo user shows the role User

Apollo’s user record carries no role field, so every Access row is recorded as User. Review actual permissions in Apollo under Settings → Manage Users.

How do I check whether the connection is healthy?

Open Integrations in the DSALTA sidebar, stay on the Connected tab, and click Manage on the integration’s card. Open the Status tab: it shows either Connected and working properly or Connection issues detected.Use the Status tab, not Overview — Overview always reports Connected regardless of the real state.

A check shows Failed and nothing changed on my side

On an integration-powered check, Failed normally means DSALTA was blocked rather than that you are non-compliant. Open the test, go to Source Data, and read the result code: 403 is a missing permission, 428 is a setting DSALTA still needs, 500 is a failure on DSALTA’s side.A real compliance gap shows 207 and leaves the test looking Completed. See Understanding Test Results.

Data looks out of date

Compliance checks re-run once a day at 02:00 America/New_York. To refresh sooner, open Integrations → Connected and click Sync from integrations at the top right — it refreshes every connected integration at once.

How do I repair a broken connection?

There is no Reconnect, Repair or Refresh Token button. The only repair available is to disconnect and connect again.

Disconnecting is destructive and cannot be undone. DSALTA removes the access records, inventory, vulnerabilities, code changes, incidents and device records collected from this integration, and deletes the test results tied to the connection. Export anything you still need as audit evidence first — see Integration errors.

Configure scope will not let me change anything

That is expected. Configure scope is read-only — it shows what DSALTA is permitted to read, and has no Save action. To change what DSALTA can see, change the permissions on the credential in the third-party product, then disconnect and connect again.

An Apollo master API key, entered in Nango’s secure window. Read-only.Before you begin

An Apollo account that can create API keys. A standard Apollo account works; no specific paid plan is required to create a key.
A master API key — a scoped key cannot list your team members.

You will need:

Field	Where to find it	Example
Master API key	Apollo → Settings → Integrations → API	`Shown when the key is created`

Start in DSALTA

Open Integrations in the DSALTA sidebar, find Apollo, and click Connect to open the connect panel. Leave it open — it lists every value you need, and you create those in the steps below.

Open Apollo's API Keys settings

In Apollo, go to Settings → Integrations → API. A standard Apollo account works; no specific paid plan is required to create a key.

Apollo's left sidebar with Admin Settings selected and the Team & Workspace setup flyout open, showing the Integrations entry

Apollo's Settings Integrations list with the API row and its Connect button

Create a key and toggle "Set as master key"

Click Create new key, name it (e.g. DSALTA). Do NOT select individual endpoint checkboxes — instead toggle “Set as master key”. The member-list endpoint DSALTA needs (“Get a List of Users”) requires a master key. Copy the key shown — you’ll paste it in the next step.

A master key is not scoped to the user list — it can reach every endpoint your Apollo plan exposes. DSALTA only ever calls /v1/users/search, but the key you are creating is broader than that call. Treat it as a secret, and revoke it in Apollo if you disconnect the integration.

Apollo's API keys page listing existing keys, with the API keys nav item and the Create new key button

Apollo's Create new API key dialog showing Name, Description, an APIs checkbox list, and the Set as master key toggle switched on

Connect Apollo

Back in the connect panel, click through to the Connect Apollo step and enter your Apollo credentials in the secure Nango window. DSALTA never stores them directly — it keeps only a connection reference, and the key itself is held by Nango.

The Link Apollo Account window with its API key field and Connect button

DSALTA validates the credential as soon as the Nango window closes, by requesting a single user from /v1/users/search. On success the integration moves to the Connected tab, and Manage → Status reads Connected and working properly. Checks begin reporting after the first sync.

If the connection is rejected. The key is invalid, revoked, or not a master key.The on-screen message is generic — see Connection error messages.

Each check below re-runs once a day, at 02:00 America/New_York, while this integration is connected. Click any check for step-by-step remediation guidance.

Check	Severity	What it verifies
User access to Critical System should be valid	Info	Checks that everyone with Apollo access is an active employee on the People page.
Offboarded users should not have active access	High	Checks that offboarded employees no longer have active Apollo access.

Getting Connected

Identity Providers

Cloud Infrastructure

Code Repositories

Security & Monitoring

Databases

SaaS & Productivity

What DSALTA reads

Troubleshooting

Topic	Link
General	Apollo website
DSALTA	Connection error messages

​What DSALTA reads

​Troubleshooting

What DSALTA reads

Troubleshooting