API Usage Guidelines

Overview

Procore’s REST APIs are designed for transactional use cases — creating, reading, updating, and deleting individual records within the Procore platform. These APIs power the day-to-day operations that keep construction projects moving.

This page covers what REST APIs are intended for, what they are not intended for, and best practices for staying in compliance.

If your use case involves AI agents, semantic retrieval, or large-scale analytics, see Agentic APIs for the intended path.

Permitted use cases

REST APIs are built for transactional workflows that complement your app’s core integration:

• Creating or updating records such as RFIs, submittals, or daily logs
• Reading project details, user information, or financial data
• Automating workflows triggered by changes in Procore
• Powering embedded apps that surface external data inside Procore
  
  

What REST APIs are not designed for

Procore’s transactional REST APIs are not intended for:

• Large-scale data extraction or bulk export for purposes outside of your app’s core integration
• Building datasets for training, fine-tuning, or benchmarking AI/ML models (including LLMs)
• Scraping, harvesting, or creating copies of Procore data
• High-volume data retrieval to power non-complementary analytics or intelligence solutions

These activities can impact platform stability, degrade performance for customers, and violate Procore’s Developer Policy and API Terms of Use.

Best practices

To maintain platform performance and stay in compliance:

• Use APIs for their intended purpose. REST APIs are built for transactional workflows — use them to create, read, update, and delete records as part of your integration’s core functionality.
• Respect rate limits. Procore enforces rate limits to ensure fair access and platform stability for all users.
• Request only the data you need. Use filters, pagination, and targeted queries rather than broad data pulls.
• Store data responsibly. Only retain Procore data that is necessary for your app’s operation. See the Developer Policy for data handling requirements.
  
  

See also

• REST API Reference
• Rate Limiting
• Agentic APIs — for AI agents, semantic retrieval, and advanced analytics use cases
• Developer Policy
• API Terms of Use
  
  

Need Help?

We’re here to support you at every step of your journey. Here’s how to get help:

You can also explore our learning tools and support resources in the Help & Learning Center.