tap-apollo
tap-apollo is a Singer tap for Apollo.io, built with the
Meltano Singer SDK. It extracts the records your team
manages in Apollo (contacts, accounts, deals, tasks, calls, sequences and
outreach emails) plus workspace reference data, through the
Apollo REST API.
Streams
| Stream | Endpoint | Replication |
|---|---|---|
contacts |
POST /contacts/search |
Incremental on updated_at |
accounts |
POST /accounts/search |
Full table |
opportunities |
GET /opportunities/search |
Full table |
tasks |
POST /tasks/search |
Full table |
phone_calls |
GET /phone_calls/search |
Full table |
sequences |
POST /emailer_campaigns/search |
Full table |
emailer_messages |
GET /emailer_messages/search |
Full table |
users |
GET /users/search |
Full table |
email_accounts |
GET /email_accounts |
Full table |
lists |
GET /labels |
Full table |
custom_fields |
GET /typed_custom_fields |
Full table |
contact_stages |
GET /contact_stages |
Full table |
account_stages |
GET /account_stages |
Full table |
opportunity_stages |
GET /opportunity_stages |
Full table |
Limitations
-
50,000 records per search. Apollo's search endpoints return at most 500 pages of 100 records. When a stream hits that cap, the tap logs a warning and stops. Apollo has no updated-since filter, so
contactsis requested newest first and pagination stops at the bookmark. After the first sync, each run only needs to page through contacts that changed since the last run. -
API key access. Apollo API keys are scoped to the endpoints chosen when they're created, and a stream fails with a 403 if the key can't call its endpoint. A master API key can call every endpoint;
phone_callsalways requires one. Otherwise, give the key access to each selected stream's endpoint, or deselect the stream. -
Rate limits and timeouts. Apollo limits calls per minute, hour and day, depending on your plan. The tap retries 429 responses, honoring
Retry-Afterwhen Apollo sends it. It also retries requests that time out, either on Apollo's side (a 422 saying "request timed out") or after 60 seconds without a response. -
Schemas. Schemas in
tap_apollo/schemas/are generated byscripts/gen_schemas.pyfrom Apollo's OpenAPI spec and examples, plus real records from the API, because the spec leaves out many fields. Fields not in a schema are dropped, with a warning. To pick up new fields, save a sample of records per stream (one<stream>.jsonarray each, kept out of git since they hold customer data) and rerun the script. Existing fields are only ever widened, never narrowed. Nested objects keep keys their schema doesn't list, such as custom field values keyed by ID:curl -sSLo spec.json https://docs.apollo.io/openapi/apollo-rest-api.json python scripts/gen_schemas.py spec.json tap_apollo/schemas path/to/samples
-
Fields with varying types are strings. Where Apollo returns a field as different types (say, a string in one record and an object in another), or the type is unknown because it was null in every sample, the field is declared as a string, and values of other types are emitted JSON-encoded (
true,{"title": "CTO"}). A column that mixes objects and plain values breaks some targets.
Configuration
| Setting | Required | Description |
|---|---|---|
api_key |
Yes | Apollo API key (Settings → Integrations → API). |
start_date |
No | Earliest update time to extract for contacts. |
The SDK also supports stream_maps, flattening_enabled and the other standard
settings. Run tap-apollo --about to list them all.
Settings can also be set via environment variables, e.g. TAP_APOLLO_API_KEY
(see .env.example), when the tap runs with --config=ENV.
Usage with Meltano
Add the tap to a Meltano project as a custom extractor:
plugins:
extractors:
- name: tap-apollo
namespace: tap_apollo
pip_url: git+https://github.com/<org>/tap-apollo.git
capabilities: [state, catalog, discover, about, stream-maps, structured-logging]
settings:
- name: api_key
kind: string
sensitive: true
- name: start_date
kind: date_iso8601
settings_group_validation:
- [api_key]
meltano install extractor tap-apollo
meltano config tap-apollo set api_key <key>
meltano run tap-apollo target-jsonl
Development
uv sync
uv run pytest # offline tests with a mocked API
TAP_APOLLO_API_KEY=<key> uv run pytest # also runs the SDK's standard tests live
uv run tap-apollo --config .secrets/config.json --discover
meltano.yml in this repo is set up for local testing:
meltano install
meltano run tap-apollo target-jsonl
Metadata
Release files for meltanolabs-tap-apollo 0.1.5
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| meltanolabs_tap_apollo-0.1.5.tar.gz | 259.9 kB | With provenance | Details for meltanolabs_tap_apollo-0.1.5.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| meltanolabs_tap_apollo-0.1.5-py3-none-any.whl | Python 3 | none | any | Details for meltanolabs_tap_apollo-0.1.5-py3-none-any.whl |
Total release size: 295.7 kB
Release files / meltanolabs_tap_apollo-0.1.5.tar.gz
| Download URL | meltanolabs_tap_apollo-0.1.5.tar.gz |
|---|---|
| Size | 259.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
da8682422449bae26b3a1128f2454a4763507da88ff24a096aedea12030db7a5
|
|
BLAKE2b-256 checksum How to use checksums |
377656a2baed5df336cb7c13b27848847ac6bfea982594a51af5d26582cf57c3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 29, 2026.
Transparency logRelease files / meltanolabs_tap_apollo-0.1.5-py3-none-any.whl
| Download URL | meltanolabs_tap_apollo-0.1.5-py3-none-any.whl |
|---|---|
| Size | 35.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
b1b46a252c68e02a992443a55035e3ed1b4681d3c1762bd79bb33375980c5b1e
|
|
BLAKE2b-256 checksum How to use checksums |
665b10a29cbcb22da0848a371f4f1148d8fb2d63221b90a317ce7563973b3b58
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 29, 2026.
Transparency logSecurity for meltanolabs-tap-apollo 0.1.5
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
Both files in this release have been uploaded with provenance metadata.
Attestation for meltanolabs_tap_apollo-0.1.5.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 29, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.