API Usage Guidelines

Overview

Procore offers a comprehensive set of REST APIs that power integrations across the construction industry. As the platform evolves to support new capabilities — including AI-driven intelligence — it’s important to understand how each set of APIs is designed to be used and where we’re headed.

The Future: Agentic APIs (Coming Soon)

Procore is developing a new generation of Agentic APIs, purpose-built to power AI agents, Retrieval-Augmented Generation (RAG) solutions, and advanced analytics. These APIs are being designed on Procore’s Datagrid infrastructure to deliver the performance, scale, and security that data-intensive AI workloads require.

With Agentic APIs, partners and developers will be able to build intelligent solutions that go beyond simple data transactions — enabling AI-powered insights, semantic retrieval, and deep analytics without the need for specialized infrastructure or external data storage.

Timeline: General Availability is planned for Late Q1 2026. Stay tuned to our Announcements page for updates.

Procore’s REST APIs: Designed for Transactional Use

Procore’s existing 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.

Common transactional use cases

• Syncing project data between Procore and an external system
• 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 the 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 outside the scope of your application’s purpose
• 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.

Choosing the Right API for Your Use Case

As Procore’s API ecosystem expands, choosing the right tool for the job ensures the best experience for you and your customers.

Best Practices for API Usage

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 application’s operation. See our Developer Policy for data handling requirements.
• Wait for Agentic APIs if your use case involves AI workloads, large-scale analytics, or semantic retrieval. Building on the right foundation from the start saves rework later.
  
  

See Also

• REST API Reference
• Rate Limiting
• Procore Developer Policy
• API Terms of Use
• Announcements
  
  

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.