Aha-io Python API Docs | dltHub

Aha! is a product development platform (roadmaps, ideas, releases) that exposes a REST API to create and extract product, release, feature and idea data. The REST API base URL is https://{account}.aha.io/api/v1 and all requests require a Bearer token (API key or OAuth2 access 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 Aha-io data in under 10 minutes.

---

What data can I load from Aha-io?

Here are some of the endpoints you can load from Aha-io:

---

How do I authenticate with the Aha-io API?

Include Authorization: Bearer header. API keys generated in UI are used as bearer tokens; OAuth2 access tokens are accepted similarly.

1. Get your credentials

1. Sign in to your Aha! account at https://{account}.aha.io. 2) Go to Settings → Account → API keys or visit https://secure.aha.io/settings/api_keys. 3) Click Create API key, give it a name, copy the generated key. 4) Use the key as the Bearer token in the Authorization header.

2. Add them to .dlt/secrets.toml

Copy
[sources.aha_io_source]
api_key = "your_aha_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 Aha-io 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 aha_io_pipeline.py

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

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

Inspect your pipeline and data:

Copy
dlt pipeline aha_io_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 features and ideas from the Aha-io 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 aha_io_source(api_key=dlt.secrets.value):
    config: RESTAPIConfig = {
        "client": {
            "base_url": "https://{account}.aha.io/api/v1",
            "auth": {
                "type": "bearer",
                "token": api_key,
            },
        },
        "resources": [
            {"name": "features", "endpoint": {"path": "features", "data_selector": "features"}},
            {"name": "ideas", "endpoint": {"path": "ideas", "data_selector": "ideas"}}
        ],
    }
    yield from rest_api_resources(config)


def get_data() -> None:
    pipeline = dlt.pipeline(
        pipeline_name="aha_io_pipeline",
        destination="duckdb",
        dataset_name="aha_io_data",
    )
    load_info = pipeline.run(aha_io_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("aha_io_pipeline").dataset()
sessions_df = data.features.df()
print(sessions_df.head())

SQL (DuckDB example):

Copy
SELECT * FROM aha_io_data.features LIMIT 10;

In a marimo or Jupyter notebook:

Copy
import dlt

data = dlt.pipeline("aha_io_pipeline").dataset()
data.features.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 Aha-io 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 failures

If you receive 403 responses, verify the Authorization header uses: Authorization: Bearer <API_KEY_OR_TOKEN>. Ensure the API key belongs to the account subdomain you are calling and that the user has sufficient permissions.

Rate limiting

Aha! enforces per-account rate limits: up to 300 requests per minute and 20 requests per second. Exceeding limits returns 429 and includes X-Ratelimit-Limit, X-Ratelimit-Remaining and X-Ratelimit-Reset headers.

Pagination

List responses are paginated. Responses include a "pagination" object and the list is returned under a resource-specific key (for example "features" for feature lists). Use page (1-indexed) and per_page (max 200) query params. Example response snippet from docs shows "pagination" and "features" keys.

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