Palantir Foundry Python API Docs | dltHub
Build a Palantir Foundry-to-database pipeline in Python using dlt with AI Workbench support for Claude Code, Cursor, and Codex.
Last updated:
Palantir Foundry is a platform for building applications on top of integrated data, providing a REST API for interacting with its Ontology and modeling resources. The REST API base URL is https://<hostname> and all requests require an Authorization header with a Bearer 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 add "dlt[hub]" and start loading Palantir Foundry data in under 10 minutes.
What data can I load from Palantir Foundry?
Here are some of the endpoints you can load from Palantir Foundry:
| Resource | Endpoint | Method | Data selector | Description |
|---|---|---|---|---|
| objects | /v2/ontologies/{ontology}/objects/{objectType} | GET | data | Lists objects for a given Ontology and object type. |
| datasets | /v2/datasets | GET | datasets | Lists all datasets. |
| table_imports | /v2/connectivity/connections/{connectionRid}/table | GET | tableImports | Lists table imports for a specific connection. |
| ontologies | /v2/ontologies | GET | ontologies | Lists all ontologies. |
| object_types | /v2/ontologies/{ontology}/objectTypes | GET | objectTypes | Lists object types for a given Ontology. |
How do I authenticate with the Palantir Foundry API?
The API uses the OAuth 2.0 protocol. Requests must include an 'Authorization' header with a bearer token formatted as 'Bearer '.
1. Get your credentials
In Palantir Foundry, you can generate a personal temporary API token by navigating to your Account settings. Locate the 'Tokens' section, which allows you to create and manage bearer tokens associated with your account. For production applications, it is highly recommended to use OAuth 2.0 (Authorization Code or Client Credentials grants) instead of static bearer tokens for better security and token lifecycle management.
2. Add them to .dlt/secrets.toml
[sources.palantir_foundry_source] token = "REPLACE_ME"
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 Palantir Foundry 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 palantir_foundry_pipeline.py
If everything is configured correctly, you'll see output like this:
Pipeline palantir_foundry_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset palantir_foundry_data The duckdb destination used duckdb:/palantir_foundry.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 /api/v2/ontologies and /api/v2/admin from the Palantir Foundry 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 palantir_foundry_source(token=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://<hostname>", "auth": {"type": "bearer", "token": token}, }, "resources": [ {"name": "objects", "endpoint": {"path": "v2/ontologies/{ontology}/objects/{objectType}", "data_selector": "data"}}, {"name": "table_imports", "endpoint": {"path": "v2/connectivity/connections/{connectionRid}/table", "data_selector": "tableImports"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="palantir_foundry_pipeline", destination="duckdb", dataset_name="palantir_foundry_data", ) load_info = pipeline.run(palantir_foundry_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("palantir_foundry_pipeline").dataset() sessions_df = data.objects.df() print(sessions_df.head())
SQL (DuckDB example):
SELECT * FROM palantir_foundry_data.objects LIMIT 10;
In a marimo or Jupyter notebook:
import dlt data = dlt.pipeline("palantir_foundry_pipeline").dataset() data.objects.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 Palantir Foundry 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 Palantir Foundry?
Request dlt skills, commands, AGENT.md files, and AI-native context.