Procore Contract-Preserving REST Client

Overview

Keep the client transport-focused and endpoint versions explicit. Procore resources use multiple REST versions, endpoint-specific page limits, company routing requirements, and actionable response headers that a generic JSON wrapper must not erase.

Prerequisites

• Enumerated public endpoints and their current reference versions
• Token-provider interface that never exposes client secrets to callers
• Typed error, pagination, rate-budget, and redaction contracts

Instructions

Step 1: Model requests explicitly

Represent HTTP method, full documented route, API version, company ID, project ID, query parameters, and body separately. Reject private or guessed routes.

Step 2: Centralize safe headers