DocuSeal Python API Docs | dltHub

DocuSeal is a REST API platform for creating, sending and managing fillable document templates and electronic signature workflows. The REST API base URL is https://api.docuseal.com and all requests require an X-Auth-Token API key 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 DocuSeal data in under 10 minutes.

---

What data can I load from DocuSeal?

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

---

How do I authenticate with the DocuSeal API?

DocuSeal uses an API key passed in the X-Auth-Token request header for authentication. Include X-Auth-Token: YOUR_API_KEY on every request.

1. Get your credentials

1. Sign up / sign in at https://www.docuseal.com or https://console.docuseal.com/api.
2. Open Settings → API (or visit the API console).
3. Copy the provided API key (X-Auth-Token).
4. Keep the key secret and use it in requests.

2. Add them to .dlt/secrets.toml

Copy
[sources.docuseal_source]
api_key = "your_docuseal_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 DocuSeal 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 docuseal_pipeline.py

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

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

Inspect your pipeline and data:

Copy
dlt pipeline docuseal_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 templates and submissions from the DocuSeal 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 docuseal_source(api_key=dlt.secrets.value):
    config: RESTAPIConfig = {
        "client": {
            "base_url": "https://api.docuseal.com",
            "auth": {
                "type": "api_key",
                "api_key": api_key,
            },
        },
        "resources": [
            {"name": "templates", "endpoint": {"path": "templates", "data_selector": "data"}},
            {"name": "submissions", "endpoint": {"path": "submissions", "data_selector": "data"}}
        ],
    }
    yield from rest_api_resources(config)


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

SQL (DuckDB example):

Copy
SELECT * FROM docuseal_data.submissions LIMIT 10;

In a marimo or Jupyter notebook:

Copy
import dlt

data = dlt.pipeline("docuseal_pipeline").dataset()
data.submissions.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 DocuSeal 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 401 Unauthorized, ensure X-Auth-Token header contains a valid API key. Example header: X-Auth-Token: YOUR_API_KEY. Regenerate the key from the DocuSeal API console if compromised.

Rate limits and pagination

List endpoints return pagination metadata in the response object under the "pagination" key and the records list under "data". Use query params limit (default 10, max 100), after and before or pagination.next values to page through results.

Common error responses

• 400 Bad Request: malformed request body or invalid parameters. Check required fields and JSON structure.
• 401 Unauthorized: missing or invalid X-Auth-Token.
• 404 Not Found: resource id does not exist.
• 422 Unprocessable Entity: validation errors when creating/updating resources. For list endpoints, empty results return data: [] with pagination reflecting count.

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