Everyaction Python API Docs | dltHub
Build a Everyaction-to-database pipeline in Python using dlt with AI harness support for Claude Code, Cursor, and Codex.
Last updated:
EveryAction (formerly NGP VAN) REST API provides access to CRM data for nonprofits and political campaigns, including contributions, events, and voter file information. The REST API base URL is https://api.securevan.com/v4 and all requests require HTTP Basic authentication via the Authorization header.
dlt is an open-source Python library that handles authentication, pagination, and schema evolution automatically. dlthub provides AI context files that enable code assistants to generate production-ready pipelines. Install with uv add "dlt[hub]" and start loading Everyaction data in under 10 minutes.
What data can I load from Everyaction?
Here are some of the endpoints you can load from Everyaction:
| Resource | Endpoint | Method | Data selector | Description |
|---|---|---|---|---|
| people | /people | GET | items | Retrieve a paginated list of contacts |
| activist_codes | /activistCodes | GET | items | Retrieve all available activist codes |
| events | /events | GET | items | List events and forms |
| contributions | /contributions | GET | items | List contributions and donations |
| saved_lists | /savedlists | GET | items | Retrieve saved lists and list metadata |
How do I authenticate with the Everyaction API?
Authentication is performed using HTTP Basic authentication, where the username is the application name and the password is the API key appended with a database-mode identifier (e.g., 'APIKey|0'). The credentials must be provided via the 'Authorization' header in the format 'Basic <base64_encoded_credentials>'.
1. Get your credentials
API key generation must be performed by an administrative user within the EveryAction CRM interface. Navigate to the 'API Integrations' section from the sidebar. If your integration is not already listed, use the 'Request an API Key' option to submit a request to your organization's administrative user. Once the request is approved by an administrator, the key can be generated directly within the 'API Keys' section by clicking 'Generate API Key'. Note that production keys should be requested through the CRM by your client; vendors cannot request them on behalf of the client.
2. Add them to .dlt/secrets.toml
[sources.everyaction_source] everyaction_app_name = "your_application_name" everyaction_api_key = "your_api_key_guid|1"
dlt reads this automatically at runtime — never hardcode tokens in your pipeline script. For production environments, see setting up credentials with dlt for environment variable and vault-based options.
How do I set up and run the pipeline?
Set up a virtual environment and install dlt:
uv init uv add "dlt[hub]"
1. Install the dlt AI harness:
uv run dlthub ai init --agent <your-agent> # <agent>: claude | cursor | codex
This installs project rules, a secrets management skill, appropriate ignore files, and configures the dlt MCP server for your agent. Learn more →
2. Install the rest-api-pipeline toolkit:
uv run dlthub ai toolkit install rest-api-pipeline
This loads the skills and context about dlt the agent uses to build the pipeline iteratively, efficiently, and safely. The agent uses MCP tools to inspect credentials — it never needs to read your secrets.toml directly. Learn more →
3. Start LLM-assisted coding:
Use /find-source to load data from the Everyaction API into DuckDB.
The rest-api-pipeline toolkit takes over from here — it reads relevant API documentation, presents you with options for which endpoints to load, and follows a structured workflow to scaffold, debug, and validate the pipeline step by step.
4. Run the pipeline:
uv run python everyaction_pipeline.py
If everything is configured correctly, you'll see output like this:
Pipeline everyaction_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset everyaction_data The duckdb destination used duckdb:/everyaction.duckdb location to store data Load package 1749667187.541553 is LOADED and contains no failed jobs
Inspect your pipeline and data:
uv run dlthub show
This opens the Pipeline Dashboard where you can verify pipeline state, load metrics, schema (tables, columns, types), and query the loaded data directly.
Python pipeline example
This example loads apiKeyProfiles and people from the Everyaction API into DuckDB. It mirrors the endpoint and data selector configuration from the table above:
import dlt from dlt.sources.rest_api import RESTAPIConfig, rest_api_resources @dlt.source def everyaction_source(api_key=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://api.securevan.com/v4", "auth": {"type": "http_basic", "username": "REPLACE_ME", "password": api_key}, }, "resources": [ {"name": "people", "endpoint": {"path": "people", "data_selector": "items"}}, {"name": "events", "endpoint": {"path": "events", "data_selector": "items"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="everyaction_pipeline", destination="duckdb", dataset_name="everyaction_data", ) load_info = pipeline.run(everyaction_source()) print(load_info)
To add more endpoints, append entries from the resource table to the "resources" list using the same name, path, and data_selector pattern.
How do I query the loaded data?
Once the pipeline runs, dlt creates one table per resource. You can query with Python or SQL.
Python (pandas DataFrame):
import dlt data = dlt.pipeline("everyaction_pipeline").dataset() sessions_df = data.people.df() print(sessions_df.head())
SQL (DuckDB example):
SELECT * FROM everyaction_data.people LIMIT 10;
In a marimo or Jupyter notebook:
import dlt data = dlt.pipeline("everyaction_pipeline").dataset() data.people.df().head()
See how to explore your data in marimo Notebooks and how to query your data in Python with dataset.
What destinations can I load Everyaction data to?
dlt supports loading into any of these destinations — only the destination parameter changes:
| Destination | Example value |
|---|---|
| DuckDB (local, default) | "duckdb" |
| PostgreSQL | "postgres" |
| BigQuery | "bigquery" |
| Snowflake | "snowflake" |
| Redshift | "redshift" |
| Databricks | "databricks" |
| Filesystem (S3, GCS, Azure) | "filesystem" |
Change the destination in dlt.pipeline(destination="snowflake") and add credentials in .dlt/secrets.toml. See the full destinations list.
Next steps
Continue your data engineering journey with the other toolkits of the dltHub AI harness:
data-exploration— Build custom notebooks, charts, and dashboards for deeper analysis with marimo notebooks.dlthub-platform— Deploy, schedule, and monitor your pipeline in production.
uv run dlthub ai toolkit install data-exploration uv run dlthub ai toolkit install dlthub-platform
Was this page helpful?
Community Hub
Need more dlt context for Everyaction?
Request dlt skills, commands, AGENT.md files, and AI-native context.