Affinity Python API Docs | dltHub

Affinity is a relationship intelligence platform that provides a REST API to access people, organizations, notes, lists and related data. The REST API base URL is https://api.affinity.co/ and All requests require either HTTP Basic authentication using the API key or a Bearer token in 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 pip install "dlt[workspace]" and start loading Affinity data in under 10 minutes.

---

What data can I load from Affinity?

Here are some of the endpoints you can load from Affinity:

---

How do I authenticate with the Affinity API?

Authentication can be performed via HTTP Basic Auth (username = API key, password empty) or by supplying a Bearer token in the Authorization: Bearer <APIKEY> header.

1. Get your credentials

1. Log in to your Affinity account.
2. Navigate to Settings → API Keys (or use the developer portal link).
3. Click Create New API Key and give it a descriptive name.
4. Copy the generated key; it will not be shown again.
5. Store the key securely and use it as the username for HTTP Basic or as the Bearer token in the Authorization header.

2. Add them to .dlt/secrets.toml

Copy
[sources.affinity_source]
api_key = "your_api_key_here"

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:

Copy
uv venv && source .venv/bin/activate
uv pip install "dlt[workspace]"

1. Install the dlt AI Workbench:

Copy
dlt 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:

Copy
dlt ai toolkit rest-api-pipeline install

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 Affinity 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:

Copy
python affinity_pipeline.py

If everything is configured correctly, you'll see output like this:

Copy
Pipeline affinity_pipeline load step completed in 0.26 seconds
1 load package(s) were loaded to destination duckdb and into dataset affinity_data
The duckdb destination used duckdb:/affinity.duckdb location to store data
Load package 1749667187.541553 is LOADED and contains no failed jobs

Inspect your pipeline and data:

Copy
dlt pipeline affinity_pipeline 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 people and organizations from the Affinity API into DuckDB. It mirrors the endpoint and data selector configuration from the table above:

Copy
import dlt
from dlt.sources.rest_api import RESTAPIConfig, rest_api_resources

@dlt.source
def affinity_source(api_key=dlt.secrets.value):
    config: RESTAPIConfig = {
        "client": {
            "base_url": "https://api.affinity.co/",
            "auth": {
                "type": "bearer",
                "token": api_key,
            },
        },
        "resources": [
            {"name": "people", "endpoint": {"path": "people"}},
            {"name": "organizations", "endpoint": {"path": "organizations/{organization_id}"}}
        ],
    }
    yield from rest_api_resources(config)


def get_data() -> None:
    pipeline = dlt.pipeline(
        pipeline_name="affinity_pipeline",
        destination="duckdb",
        dataset_name="affinity_data",
    )
    load_info = pipeline.run(affinity_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):

Copy
import dlt

data = dlt.pipeline("affinity_pipeline").dataset()
sessions_df = data.people.df()
print(sessions_df.head())

SQL (DuckDB example):

Copy
SELECT * FROM affinity_data.people LIMIT 10;

In a marimo or Jupyter notebook:

Copy
import dlt

data = dlt.pipeline("affinity_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 Affinity data to?

dlt supports loading into any of these destinations — only the destination parameter changes:

Change the destination in dlt.pipeline(destination="snowflake") and add credentials in .dlt/secrets.toml. See the full destinations list.

---

Troubleshooting

Authentication Errors

If you receive a 401 Unauthorized response, verify that your API key is correct and that you are using the proper authentication method (Basic or Bearer). An invalid or missing key will trigger this error.

Rate Limiting

The API enforces per‑user and per‑organization limits. When a 429 Too Many Requests response is returned, examine the X‑Ratelimit‑Limit‑User‑Remaining and X‑Ratelimit‑Limit‑Org‑Remaining headers. Reduce request frequency or implement exponential back‑off.

Server Errors

Responses like 500 Internal Server Error or 503 Service Unavailable indicate temporary issues on Affinity’s side. Retry the request after a brief pause; if the problem persists, contact Affinity support.

Ensure that the API key is valid to avoid 401 Unauthorized errors. Also, verify endpoint paths and parameters to avoid 404 Not Found errors.

---

Next steps

Continue your data engineering journey with the other toolkits of the dltHub AI Workbench:

• data-exploration — Build custom notebooks, charts, and dashboards for deeper analysis with marimo notebooks.
• dlthub-runtime — Deploy, schedule, and monitor your pipeline in production.

Copy
dlt ai toolkit data-exploration install
dlt ai toolkit dlthub-runtime install

• How to deploy a pipeline
• How to explore your data in marimo Notebooks
• How to query your data in Python with dataset
• Join the dlt community on Slack