Procore APIConnect Procore without building on its API
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. If you're reading the docs because you need Procore to talk to the rest of your stack, Caddi does that without you writing or maintaining integration code: you show it the job once, and it runs it across Procore and your other tools.
- APIREST (JSON)
- AuthOAuth 2.0
- AccessSelf-serve
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.
Building on the Procore API vs. having Caddi run it
| The job | Build it on the API | With Caddi |
|---|---|---|
| Getting access | Register an app, get Procore credentials, and manage tokens and refreshes. | Connect your Procore account once. Caddi holds the connection. |
| Writing the integration | A developer maps fields, handles pagination, retries and rate limits, and writes the sync. | You show Caddi the Procore task the way you'd train a new hire. It writes verified code for it. |
| Steps the API doesn't cover | Screens with no endpoint stay manual, or need a separate RPA tool. | Caddi uses a secure, audited browser session where there's no API, in the same automation. |
| The other systems in the loop | Each extra tool is another API, another set of credentials, another integration to own. | One automation runs across all the tools the job touches. |
| Keeping it running | Someone owns the code when the API version, fields or your process change. | Every automation is reviewed before it runs in production, and every run is logged. |
Building on the API is the right call when you have engineers and the integration is your product. When the goal is getting Procore work off someone's desk, the build is the slow part.
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.
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. Where a step has no API, Caddi uses a secure, audited browser session in the same automation.
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.
Connect Procore without the build.
Drop your work email and pick a time. We'll show you Caddi running your Procore workflow end to end.