Ironclad Python API Docs | dltHub

Build a Ironclad-to-database pipeline in Python using dlt with AI Workbench support for Claude Code, Cursor, and Codex.

Last updated:

Ironclad is a contract lifecycle management and clickwrap platform providing a REST API for managing workflows, contracts, and clickwrap agreements. The REST API base URL is https://api.ironcladapp.com and All requests require a Bearer token for authentication..

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 Ironclad data in under 10 minutes.


What data can I load from Ironclad?

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

ResourceEndpointMethodData selectorDescription
workflows/workflowsGETList all workflows (rate limited to 400 req/min).
records/recordsGETRetrieve records (rate limited to 600 req/min).
workflow_detail/workflows/{workflow_id}GETRetrieve a single workflow by ID.
templates/templatesGETList contract templates.
contracts/contractsGETList contracts.

How do I authenticate with the Ironclad API?

Include an HTTP header Authorization: Bearer YOUR_ACCESS_TOKEN with each request.

1. Get your credentials

  1. Log in to Ironclad and navigate to your User Profile.
  2. Locate the “API Keys” section and click the plus (+) sign to open the “Register an API Key” modal.
  3. Click “Register” to generate a client secret and access token.
  4. Copy the displayed client secret and access token; they will not be shown again.
  5. Store the access token securely for use in API calls.

2. Add them to .dlt/secrets.toml

[sources.ironclad_source] access_token = "your_access_token_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:

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

1. Install the dlt AI Workbench:

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:

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

python ironclad_pipeline.py

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

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

Inspect your pipeline and data:

dlt pipeline ironclad_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 workflows and records from the Ironclad 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 ironclad_source(access_token=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://api.ironcladapp.com", "auth": { "type": "bearer", "token": access_token, }, }, "resources": [ {"name": "workflows", "endpoint": {"path": "workflows"}}, {"name": "records", "endpoint": {"path": "records"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="ironclad_pipeline", destination="duckdb", dataset_name="ironclad_data", ) load_info = pipeline.run(ironclad_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("ironclad_pipeline").dataset() sessions_df = data.workflows.df() print(sessions_df.head())

SQL (DuckDB example):

SELECT * FROM ironclad_data.workflows LIMIT 10;

In a marimo or Jupyter notebook:

import dlt data = dlt.pipeline("ironclad_pipeline").dataset() data.workflows.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 Ironclad data to?

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

DestinationExample 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.


Troubleshooting

Authentication Errors

If the Authorization header is missing or the token is invalid, the API will return a 401 Unauthorized response.

Rate Limiting

GET endpoints are limited (e.g., 400 requests/min for /workflows, 600 requests/min for /records). Exceeding these limits returns a 429 Too Many Requests status code.

Pagination

Most list endpoints use standard page and page_size query parameters; ensure to follow the next cursor provided in the response to retrieve subsequent pages.

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.
dlt ai toolkit data-exploration install dlt ai toolkit dlthub-runtime install

Was this page helpful?

Community Hub

Need more dlt context for Ironclad?

Request dlt skills, commands, AGENT.md files, and AI-native context.