DocuSign Python API Docs | dltHub
Build a DocuSign-to-database pipeline in Python using dlt with AI Workbench support for Claude Code, Cursor, and Codex.
Last updated:
DocuSign's REST API allows document generation and management of envelopes, enabling the creation of reusable templates and the sending of signed documents. The API supports various document types and attachments. Essential methods include creating envelopes and managing documents. The REST API base URL is https://demo.docusign.net/restapi and All requests require an OAuth 2.0 Bearer access token..
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 DocuSign data in under 10 minutes.
What data can I load from DocuSign?
Here are some of the endpoints you can load from DocuSign:
| Resource | Endpoint | Method | Data selector | Description |
|---|---|---|---|---|
| accounts | accounts/{accountId} | GET | Get account info (via /oauth/userinfo and accounts APIs that return base_uri) | |
| envelopes | accounts/{accountId}/envelopes | GET | envelopes | List envelopes for an account (returns envelopes array) |
| envelope | accounts/{accountId}/envelopes/{envelopeId} | GET | Get envelope details (single object) | |
| envelope_documents | accounts/{accountId}/envelopes/{envelopeId}/documents | GET | envelopeDocuments | List documents in an envelope (envelopeDocuments array) |
| envelope_recipients | accounts/{accountId}/envelopes/{envelopeId}/recipients | GET | signers (and other recipient arrays within response) | Get recipients for an envelope (response contains recipient role arrays such as signers) |
| templates | accounts/{accountId}/templates | GET | envelopeTemplates | List templates for an account |
| users | accounts/{accountId}/users | GET | users | List users in the account |
| folders | accounts/{accountId}/folders | GET | folders | List folders |
How do I authenticate with the DocuSign API?
Use OAuth 2.0 (Authorization Code or JWT Grant) to obtain an access token; include header Authorization: Bearer <access_token> on every request. The /oauth/userinfo endpoint returns account information and the base_uri for API requests.
1. Get your credentials
- Sign in to DocuSign Developer account (demo environment).
- In the Admin -> Apps and Keys (Integrations) create an Integration Key (Client ID).
- For Authorization Code: set Redirect URI and generate a secret; for JWT: create and upload an RSA key pair and add a user consent.
- Use OAuth flows to exchange credentials for an access token.
2. Add them to .dlt/secrets.toml
[sources.docusign_esign_source] access_token = "YOUR_OAUTH_ACCESS_TOKEN"
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 DocuSign 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 docusign_esign_pipeline.py
If everything is configured correctly, you'll see output like this:
Pipeline docusign_esign_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset docusign_esign_data The duckdb destination used duckdb:/docusign_esign.duckdb location to store data Load package 1749667187.541553 is LOADED and contains no failed jobs
Inspect your pipeline and data:
dlt pipeline docusign_esign_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 envelopes and envelope_documents from the DocuSign 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 docusign_esign_source(access_token=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://demo.docusign.net/restapi", "auth": { "type": "bearer", "token": access_token, }, }, "resources": [ {"name": "envelopes", "endpoint": {"path": "accounts/{accountId}/envelopes", "data_selector": "envelopes"}}, {"name": "envelope_documents", "endpoint": {"path": "accounts/{accountId}/envelopes/{envelopeId}/documents", "data_selector": "envelopeDocuments"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="docusign_esign_pipeline", destination="duckdb", dataset_name="docusign_esign_data", ) load_info = pipeline.run(docusign_esign_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("docusign_esign_pipeline").dataset() sessions_df = data.envelopes.df() print(sessions_df.head())
SQL (DuckDB example):
SELECT * FROM docusign_esign_data.envelopes LIMIT 10;
In a marimo or Jupyter notebook:
import dlt data = dlt.pipeline("docusign_esign_pipeline").dataset() data.envelopes.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 DocuSign data to?
dlt supports loading into any of these destinations — only the destination parameter changes:
| Destination | Example 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.
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 DocuSign?
Request dlt skills, commands, AGENT.md files, and AI-native context.