Load Requirement Yogi data to DuckDB

Requirement Yogi is a requirement management platform that provides REST APIs for integrating with Jira and Confluence data. Everything needed to build a working Requirement Yogi → DuckDB pipeline is on this page: the API's base URL, authentication, endpoints, pagination and incremental field — plus a prompt that hands the whole job to your coding agent.

---

Build your Requirement Yogi to DuckDB pipeline

Paste this prompt into Claude, Codex, or Cursor. The agent does the rest.

PromptCopy prompt
Run uvx dlthub-init@latest to build a pipeline from Requirement Yogi to DuckDB and run it on dltHub

That scaffolds a dltHub workspace and installs the dltHub AI harness — the project rules, the secrets-management skill, and the dlt MCP server your agent needs to work safely. From there it reads the Requirement Yogi API, proposes the endpoints to load, then writes, runs and validates the pipeline while you review rather than type. Credentials are inspected through MCP tools, so your agent never reads secrets.toml itself. How the LLM-native workflow works →

Prefer to write it yourself? Every fact the agent uses is below.

---

Requirement Yogi API at a glance

These values come from the Requirement Yogi API reference — the authoritative source if anything here looks out of date.

---

How do I authenticate with the Requirement Yogi API?

Authentication requires two custom headers: 'X-Base-Url' to specify the Atlassian site URL and 'X-Api-Key' to provide your generated personal access token.

1. Get your credentials

To obtain credentials for the Requirement Yogi REST API: 1. Navigate to the Requirement Yogi web application dashboard (https://app.requirementyogi.com for the EU region or https://app.us.requirementyogi.com for the US region). 2. Log in to your Requirement Yogi account. 3. Click your profile icon in the top navigation bar. 4. Navigate to Settings. 5. In the left sidebar, select Personal access tokens. 6. Click Generate new token, provide a name and expiration, and click Generate. Copy the token immediately, as it cannot be retrieved again. Ensure your Atlassian account is linked under Settings > Linked accounts to provide necessary permissions for API access.

2. Add them to .dlt/secrets.toml

Copy
[sources.requirement_yogi_source]
api_key = "your_personal_access_token_here"
base_url = "https://your-atlassian-site.atlassian.net/wiki"

dlt reads this file automatically at runtime. With the harness, the setup-secrets skill prompts you for the values and never handles the raw credential in chat. For production, see setting up credentials with dlt.

---

What Requirement Yogi data can I load into DuckDB?

These are the Requirement Yogi endpoints dlt can load into DuckDB:

---

How do I load only new Requirement Yogi records?

The Requirement Yogi API reference does not document a timestamp or sequence field for these endpoints, so there is nothing to advertise here as verified. Pick a field from the endpoints table above that increases with every write, then set it as the cursor_path.

Copy
{"name": "requirements", "endpoint": {
    "path": "rest/reqs/1/requirement2/{spaceKey}",
    # Replace with a field that increases on every write.
    "incremental": {"cursor_path": "REPLACE_ME", "initial_value": "2024-01-01T00:00:00Z"},
}}

On the first run dlt loads everything from initial_value; on every run after that it requests only what changed and appends with write_disposition="merge" if you set a primary key. See incremental loading.

---

What does the generated Requirement Yogi pipeline look like?

A standard dlt REST API pipeline — the same code you would write by hand, loading /rest/search and /rest/reqs/1/requirement2/{spaceKey} from the Requirement Yogi API into DuckDB:

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

@dlt.source
def requirement_yogi_source(api_key=dlt.secrets.value):
    config: RESTAPIConfig = {
        "client": {
            "base_url": "https://confluence.requirementyogi.com",
            "auth": {"type": "api_key", "api_key": api_key, "name": "X-Api-Key", "location": "header"},
        },
        "resources": [
            {"name": "requirements", "endpoint": {"path": "rest/reqs/1/requirement2/{spaceKey}"}},
            {"name": "baselines", "endpoint": {"path": "rest/reqs/1/baseline/{spaceKey}"}}
        ],
    }
    yield from rest_api_resources(config)


def load_requirement_yogi_to_duckdb() -> None:
    pipeline = dlt.pipeline(
        pipeline_name="requirement_yogi_pipeline",
        destination="duckdb",
        dataset_name="requirement_yogi_data",
    )
    load_info = pipeline.run(requirement_yogi_source())
    print(load_info)


if __name__ == "__main__":
    load_requirement_yogi_to_duckdb()

Run it with python requirement_yogi_pipeline.py. The agent iterates on this until it loads cleanly — you review and approve, rather than write it from scratch.

---

How do I query Requirement Yogi data in DuckDB?

dlt creates one table per resource. Query the loaded data with Python or SQL — or ask your agent to, through the MCP server's execute_sql_query tool.

Python (pandas DataFrame):

Copy
import dlt

data = dlt.pipeline("requirement_yogi_pipeline").dataset()
df = data.requirements.df()
print(df.head())

SQL:

Copy
SELECT * FROM requirement_yogi_data.requirements LIMIT 10;

See querying your data with dataset and exploring it in marimo notebooks.

---

How do I deploy the Requirement Yogi to DuckDB pipeline in production?

The pipeline runs locally, which is ideal for prototyping and one-off analysis. When you need it on a schedule, monitored on every load, and shared with your team, deploy the same dlt code on the dltHub platform — no infrastructure to maintain. The prompt above already ends with "run it on dltHub", so your agent can take it there directly.

• Deploy & schedule — run the pipeline as a managed job with automatic retries.
• Monitor — observable job queues, alerting, and load metrics for every run.
• Transform — promote raw Requirement Yogi loads into governed, documented models.
• Visualize & share — explore data in notebooks and publish live dashboards instead of static screenshots.

Book a demo →

---

What other destinations can I load Requirement Yogi data to?

dlt loads into any of these — only the destination argument changes:

Set dlt.pipeline(destination="snowflake") and add credentials in .dlt/secrets.toml. On the dltHub platform the same pipeline runs against a managed Iceberg lakehouse. See the full destinations list.

---

Next steps

• Ready for production? Book a demo of the dltHub platform →
• dlt LLM-native workflow docs
• REST API source reference
• Join the dlt community on Slack