USPTO Patent File Wrapper Python API Docs | dltHub
Build a USPTO Patent File Wrapper-to-database pipeline in Python using dlt with AI Workbench support for Claude Code, Cursor, and Codex.
Last updated:
The USPTO Patent File Wrapper API provides access to documents attached to patent applications. The endpoint is at https://data.uspto.gov/apis/patent-file-wrapper/documents. It includes JSON examples for available endpoints. The REST API base URL is https://api.uspto.gov/api/v1 and All requests require an API key..
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 USPTO Patent File Wrapper data in under 10 minutes.
What data can I load from USPTO Patent File Wrapper?
Here are some of the endpoints you can load from USPTO Patent File Wrapper:
| Resource | Endpoint | Method | Data selector | Description |
|---|---|---|---|---|
| documents | patent/applications/{applicationNumberText}/documents | GET | documentBag | Returns document metadata and download links for a given application. |
| application_data | patent/applications/{applicationNumberText}/application-data | GET | Retrieves basic application information. | |
| continuity | patent/applications/{applicationNumberText}/continuity | GET | Provides continuity data such as parent/child applications. | |
| transactions | patent/applications/{applicationNumberText}/transactions | GET | Lists transaction history for the application. | |
| search | patent/search | GET | Search API for querying patent application records. |
How do I authenticate with the USPTO Patent File Wrapper API?
Authentication is performed via an API key that must be included with each request (e.g., as a query parameter or header).
1. Get your credentials
- Open the USPTO Open Data Portal website.
- Sign in or create a USPTO user account.
- Navigate to the "API Keys" or "Developer" section.
- Request a new API key for the Patent File Wrapper API.
- Copy the generated key; it will be used as the "api_key" value in dlt.
2. Add them to .dlt/secrets.toml
[sources.uspto_patent_file_wrapper_source] api_key = "your_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:
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 USPTO Patent File Wrapper 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 uspto_patent_file_wrapper_pipeline.py
If everything is configured correctly, you'll see output like this:
Pipeline uspto_patent_file_wrapper_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset uspto_patent_file_wrapper_data The duckdb destination used duckdb:/uspto_patent_file_wrapper.duckdb location to store data Load package 1749667187.541553 is LOADED and contains no failed jobs
Inspect your pipeline and data:
dlt pipeline uspto_patent_file_wrapper_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 documents and search from the USPTO Patent File Wrapper 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 uspto_patent_file_wrapper_source(api_key=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://api.uspto.gov/api/v1", "auth": { "type": "api_key", "api_key": api_key, }, }, "resources": [ {"name": "documents", "endpoint": {"path": "patent/applications/{applicationNumberText}/documents", "data_selector": "documentBag"}}, {"name": "search", "endpoint": {"path": "patent/search"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="uspto_patent_file_wrapper_pipeline", destination="duckdb", dataset_name="uspto_patent_file_wrapper_data", ) load_info = pipeline.run(uspto_patent_file_wrapper_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("uspto_patent_file_wrapper_pipeline").dataset() sessions_df = data.documents.df() print(sessions_df.head())
SQL (DuckDB example):
SELECT * FROM uspto_patent_file_wrapper_data.documents LIMIT 10;
In a marimo or Jupyter notebook:
import dlt data = dlt.pipeline("uspto_patent_file_wrapper_pipeline").dataset() data.documents.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 USPTO Patent File Wrapper 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 USPTO Patent File Wrapper?
Request dlt skills, commands, AGENT.md files, and AI-native context.