Skip to content

Procore API

What the Procore API can do for your company.

Procore has a public, documented REST API. Through it, most of what your team does in Procore by hand can be read, created or updated by another system, within rules on authentication, company scoping and rate limits that every integration has to respect.

Written by Roberto Postolovski, Founder & Tech LeadUpdated

Today

How it works now

Without an integration, the API's work is done by people.

This page explains what the API offers in plain terms, what it takes to build on it, and when a custom integration is worth it.

  1. 01Projects are set up twice, in Procore and in every other system.
  2. 02Documents are downloaded from one place and uploaded to another.
  3. 03Reports start with an export to Excel.
  4. 04Status updates from Procore are copied into emails.
  5. 05Records drift apart because each system is updated on a different day.

The essentials

How the Procore API works

The basics, from Procore's developer documentation:

Sources

  • Authentication uses OAuth 2.0. Every request needs an access token.
  • Requests include a Procore-Company-Id header, so every call is scoped to a company.
  • Endpoints are versioned REST paths on api.procore.com, and every call must use HTTPS.
  • A sandbox environment is available for building and testing without touching live projects.
  • Two rate limits apply: an hourly limit and a spike limit over a 10-second window. Response headers report how many requests remain.
  • Webhooks can notify an integration when records change, so it can react instead of repeatedly polling.
  • Official SDKs exist for JavaScript and Ruby, and finished apps can be published to the Procore App Marketplace.

The automation

How we replace it

A Procore integration is a small software product. We build it like one.

  1. 01

    Scope

    Which records move, in which direction, how often, and which system owns each field.

  2. 02

    Prototype

    Built against the Procore sandbox with your real project structure, not against live projects.

  3. 03

    Design for limits

    Batching, webhooks and caching keep the integration within Procore's rate limits as your volume grows.

  4. 04

    Validate

    Every write is checked against both systems first. Anything that doesn't match goes to a person with the reason attached.

  5. 05

    Deploy

    Where appropriate, inside your own cloud environment, running on API credentials you control and can revoke.

  6. 06

    Monitor

    Every API call that changes data is logged, and failures are reported the same day.

What contractors typically build

  • Sync with an ERP Procore doesn't support
  • Automated project setup
  • RFI and submittal intake from email
  • Document sync with SharePoint
  • Custom reporting extracts
  • Field data to payroll

Systems involved

  • Procore REST API
  • Procore webhooks
  • Procore sandbox
  • Your ERP or database
  • Microsoft 365
  • Cloud hosting

What stays with your team

Automation should remove the repetition, not the responsibility.

  • Deciding which system owns each field
  • Approving writes that affect cost or contracts
  • Granting and revoking API access
  • Reviewing records that fail validation

What changes

Measured against your own baseline, not against a benchmark.

  • Repetitive work between Procore and other systems stops
  • The integration stays within Procore's rate limits as volume grows
  • Every change the integration makes is logged and traceable
  • You own the integration and the credentials it runs on

Questions

Common questions

Do we need a developer to use the Procore API?
To build on it, yes: OAuth, rate limits and error handling need engineering. To benefit from it, no: once an integration runs, your team keeps working in Procore and the other system as usual.
Are Procore's API rate limits a problem?
Only for integrations that ignore them. Procore enforces an hourly limit and a short spike limit; an integration that batches requests and reacts to webhooks instead of polling stays well within them.
Custom integration or an App Marketplace app?
If a Marketplace app covers your workflow, use it. It is cheaper and someone else maintains it. A custom integration makes sense when your systems, fields or rules are specific to your company.
Who owns the integration?
You do. Code, hosting and handover are agreed in writing before work starts, and the integration runs on API credentials you control and can revoke at any time.

What’s one repetitive process your team does every day?

Tell us about it. We’ll help you determine whether it can be automated, what it would take, and whether the numbers make sense.