PTC Windchill Python API Docs | dltHub
Build a PTC Windchill-to-database pipeline in Python using dlt with AI Workbench support for Claude Code, Cursor, and Codex.
Last updated:
PTC Windchill REST Services provides OData-compliant APIs to interact with Windchill product lifecycle management data. The REST API base URL is https://<windchill-host>/Windchill/servlet/odata/v5 and Supports OAuth 2.0 (Bearer) or HTTP Basic 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 add "dlt[hub]" and start loading PTC Windchill data in under 10 minutes.
What data can I load from PTC Windchill?
Here are some of the endpoints you can load from PTC Windchill:
| Resource | Endpoint | Method | Data selector | Description |
|---|---|---|---|---|
| parts | /ProdMgmt/Parts | GET | value | Retrieve a list of parts. |
| documents | /DocMgmt/Documents | GET | value | Retrieve a list of documents. |
| changes | /ChangeMgmt/ChangeNotices | GET | value | Retrieve a list of change notices. |
| users | /PTC/Users | GET | value | Retrieve a list of users. |
| projects | /ProjMgmt/Projects | GET | value | Retrieve a list of projects. |
How do I authenticate with the PTC Windchill API?
Windchill supports OAuth 2.0 where the access token is provided as a Bearer token in the 'Authorization' header. Alternatively, HTTP Basic authentication or session cookies can be used for standard API access.
1. Get your credentials
PTC Windchill REST Services (WRS) typically utilizes OAuth 2.0 for authentication rather than static API keys. To obtain credentials: 1. Ensure your Windchill instance is configured as an OAuth Resource Server and your application is registered as a Service Provider with your Central Authorization Server (CAS). 2. Direct your application to the authorization endpoint to obtain an authorization code. 3. Exchange the authorization code for an access token by sending a POST request (Content-Type: application/x-www-form-urlencoded) to the CAS token endpoint containing your client_id, client_secret, grant_type=authorization_code, and the authorization code. 4. Use the returned access_token as a Bearer Token in the Authorization header of your WRS API requests. Note that endpoints requiring OAuth must typically be accessed via URLs containing an 'oauth' prefix.
2. Add them to .dlt/secrets.toml
[sources.ptc_windchill_source] client_id = "your_client_id_here" client_secret = "your_client_secret_here" token_url = "https://your-cas-server.com/token" authorization_url = "https://your-cas-server.com/auth"
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 init uv add "dlt[hub]"
1. Install the dlt AI harness:
uv run dlthub 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:
uv run dlthub ai toolkit install rest-api-pipeline
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 PTC Windchill 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:
uv run python ptc_windchill_pipeline.py
If everything is configured correctly, you'll see output like this:
Pipeline ptc_windchill_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset ptc_windchill_data The duckdb destination used duckdb:/ptc_windchill.duckdb location to store data Load package 1749667187.541553 is LOADED and contains no failed jobs
Inspect your pipeline and data:
uv run dlthub 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 Parts and Documents from the PTC Windchill 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 ptc_windchill_source(username=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://<windchill-host>/Windchill/servlet/odata/v5", "auth": {"type": "bearer", "token": username}, }, "resources": [ {"name": "parts", "endpoint": {"path": "ProdMgmt/Parts", "data_selector": "value"}}, {"name": "documents", "endpoint": {"path": "DocMgmt/Documents", "data_selector": "value"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="ptc_windchill_pipeline", destination="duckdb", dataset_name="ptc_windchill_data", ) load_info = pipeline.run(ptc_windchill_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("ptc_windchill_pipeline").dataset() sessions_df = data.parts.df() print(sessions_df.head())
SQL (DuckDB example):
SELECT * FROM ptc_windchill_data.parts LIMIT 10;
In a marimo or Jupyter notebook:
import dlt data = dlt.pipeline("ptc_windchill_pipeline").dataset() data.parts.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 PTC Windchill 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 harness:
data-exploration— Build custom notebooks, charts, and dashboards for deeper analysis with marimo notebooks.dlthub-platform— Deploy, schedule, and monitor your pipeline in production.
uv run dlthub ai toolkit install data-exploration uv run dlthub ai toolkit install dlthub-platform
Was this page helpful?
Community Hub
Need more dlt context for PTC Windchill?
Request dlt skills, commands, AGENT.md files, and AI-native context.