Procore Python API Docs | dltHub

Build a Procore-to-database pipeline in Python using dlt with AI Workbench support for Claude Code, Cursor, and Codex.

Last updated:

Procore's REST API allows management of checklist items, with responses in formats like text, number, date, or status. The API overview highlights its advantages over the previous Vapid API. Use endpoints to list checklists and manage attachments. The REST API base URL is https://api.procore.com/rest/v1.0 and all requests require 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 Procore data in under 10 minutes.


What data can I load from Procore?

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

ResourceEndpointMethodData selectorDescription
checklistsprojects/{project_id}/checklist/listGET""Lists Checklists (Inspections) in a specified Project
checklist_itemsprojects/{project_id}/checklist/list_itemsGET"items"Lists Checklist (Inspections) Items in a specified Project
checklist_item_attachmentsprojects/{project_id}/checklist/item_attachmentsGET""Lists Checklist Item Attachments in a specified Project
checklist_sectionsprojects/{project_id}/checklist/list_sectionsGET""Lists Checklist (Inspection) Sections
checklist_item_observationsprojects/{project_id}/checklist/item_observationsGET""Lists Checklist Item Observations

How do I authenticate with the Procore API?

Procore uses OAuth 2.0 for API authentication. Obtain an access token via the OAuth flow (authorization_code or client_credentials for service accounts) and send it in the Authorization header as: Authorization: Bearer <access_token>.

1. Get your credentials

  1. Create a Procore App in the Procore Developer Dashboard. 2) For standard apps, use the OAuth authorization_code flow to get an authorization code, then exchange it for an access_token and refresh_token. For service accounts, use client_credentials to obtain an access_token. 3) Store the access_token (and refresh_token) and include the access_token in Authorization: Bearer <access_token> for API calls.

2. Add them to .dlt/secrets.toml

[sources.procore_source] access_token = "your_procore_access_token_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 Procore 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 procore_pipeline.py

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

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

Inspect your pipeline and data:

dlt pipeline procore_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 checklist_items and checklists from the Procore 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 procore_source(access_token=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://api.procore.com/rest/v1.0", "auth": { "type": "bearer", "access_token": access_token, }, }, "resources": [ {"name": "checklist_items", "endpoint": {"path": "projects/{project_id}/checklist/list_items", "data_selector": "items"}}, {"name": "checklists", "endpoint": {"path": "projects/{project_id}/checklist/list"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="procore_pipeline", destination="duckdb", dataset_name="procore_data", ) load_info = pipeline.run(procore_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("procore_pipeline").dataset() sessions_df = data.checklist_items.df() print(sessions_df.head())

SQL (DuckDB example):

SELECT * FROM procore_data.checklist_items LIMIT 10;

In a marimo or Jupyter notebook:

import dlt data = dlt.pipeline("procore_pipeline").dataset() data.checklist_items.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 Procore data to?

dlt supports loading into any of these destinations — only the destination parameter changes:

DestinationExample 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 Procore?

Request dlt skills, commands, AGENT.md files, and AI-native context.