Apollo
Overview
The Apollo connector supports:
- Source: Authenticate to Apollo and (eventually) extract data into your destination.
- Destination (Reverse ETL): Authenticate to Apollo and (eventually) load data into Apollo.
At this time, both extraction (source) and loading (destination) are still in development. You can configure the connector and validate credentials, but sync runs will not yet move data.
Requirements
- An Apollo API key with access to the Apollo API.
Authentication
Apollo uses an API key passed via the X-Api-Key header.
Create an API key in Apollo
- In Apollo, generate or copy an API key from your account/workspace settings.
- Store it securely (you’ll provide it to the connector as
api_key).
Setup
- Create a new Apollo connection.
- Enter your API key.
- Save and test the connection.
The connector validates credentials by making a request to an Apollo API endpoint using your API key.
Configuration reference
Source configuration
| Field | Type | Required | Description |
|---|---|---|---|
api_key | string | ✅ | Apollo API key used to authenticate requests. |
Destination configuration (Reverse ETL)
| Field | Type | Required | Description |
|---|---|---|---|
api_key | string | ✅ | Apollo API key used to authenticate requests. |
Streams
No streams are currently exposed. The source catalog is currently empty while extraction is in development.
Destination behavior (Reverse ETL)
Destination loading is currently in development and is not yet available for production use.
Hashing and normalization
This destination connector does not currently expose field-level hashing options.
Data contract
Not yet available. The Apollo destination is still in development and does not currently define supported objects, required identifiers, or write semantics.