Waitlist2026 State of AI at Enterprise RIAs2026 State of AI at RIAsOut Nov 6On demandOther eventsNext: AI for Mid-Sized Law, Nov 5
Procore APIIntegration guide

Integrate the Procore API.Caddi writes and runs the integration for you.

Procore has a REST API. Self-serve developer account and sandbox for anyone; production use requires installation into a Procore customer company, and Marketplace listing goes through Procore review.

  • 99%of agent runs complete successfully
  • ~45 minon average to build your first agent
  • 1M+back-office tasks completed
01Getting access

The connection is a project before it does anything.

Before the first record moves: an app registration, credentials, token refresh, and somewhere to host and monitor the code. Procore enforces an hourly (60-minute) limit and a 10-second spike limit reported via X-Rate-Limit headers, but the current docs do not state fixed numbers.

On your own

Register an app, store Procore credentials, refresh tokens and code around the rate limits.

With Caddi

Connect your Procore account once. Caddi holds the connection.

02The whole job

The job doesn't stop at Procore.

An intake, a filing or a client update also runs through email, documents and the other systems your team works in. The Procore API only reaches Procore.

On your own

Each extra system is another API, another set of credentials, another integration to own.

With Caddi

One automation runs across every tool the job touches, each through its API.

03After launch

Someone has to own the code.

API versions change, fields get added and your process moves.

On your own

A developer patches and redeploys the integration each time.

With Caddi

The person who does the work updates it by showing or describing the change. Every automation is reviewed before it runs in production, and every run is logged.

What the Procore API gives you

Type
REST (JSON)
Authentication
OAuth 2.0 (authorization code or client credentials)
Who can get access
Self-serve developer account and sandbox for anyone; production use requires installation into a Procore customer company, and Marketplace listing goes through Procore review.
What it covers
Construction project data including projects, financial tools (budgets, commitments, change orders), field tools, documents, and project management.
Limits
Procore enforces an hourly (60-minute) limit and a 10-second spike limit reported via X-Rate-Limit headers, but the current docs do not state fixed numbers.

Official docs: developers.procore.com. Checked September 2026. Vendors change access terms, so confirm with Procore before you build.

When to build the Procore integration in-house

When you have engineers and the integration is your product, or you need one narrow sync between two systems and someone to own it. When the goal is getting Procore work off someone's desk, the build is the slow part, and Caddi does it for you.

What teams usually want the Procore API for

  • Sync project docs

    Caddi moves Procore project documents into the right systems and keeps them current.

  • Push project data to finance

    Caddi carries Procore cost and project data into accounting without re-keying.

  • Reach a system Procore cannot

    Caddi automates a tool Procore has no connector for and hands the data back.

Everything Caddi does with Procore.

Procore API questions

Does Procore have an API?

Yes. Procore has a REST API, authenticated with OAuth 2.0 (authorization code or client credentials). The official documentation is at https://developers.procore.com/documentation/introduction.

How do I get access to the Procore API?

Self-serve developer account and sandbox for anyone; production use requires installation into a Procore customer company, and Marketplace listing goes through Procore review.

Does the Procore API have rate limits?

Procore enforces an hourly (60-minute) limit and a 10-second spike limit reported via X-Rate-Limit headers, but the current docs do not state fixed numbers.

Can I connect Procore to my other tools without writing code against its API?

Yes. With Caddi you show the Procore task once, the way you'd train a new hire, and Caddi builds it as verified code that runs across Procore and the other tools the job touches. Steps that need a person's judgment are handed to Copilot or Claude, and Caddi monitors those too.

Do I need a developer to automate Procore with Caddi?

No. There is no integration code for you to write or maintain. Every automation Caddi builds for Procore is reviewed before it runs in production, and every run is logged.