Procore Webhook and Reconciliation Boundary

Overview

Use webhooks for freshness and REST reconciliation for completeness. A delivery tells the receiver that a committed Procore change occurred; it is not the resource itself and may be duplicated, delayed, or discarded after prolonged endpoint failure.

Prerequisites

• Company or project scope, namespace, resource names, and event reasons
• Public HTTPS receiver that acknowledges quickly and queues work durably
• Webhooks API permission, OAuth principal, deduplication store, and reconciliation cursor

Instructions

Step 1: Choose payload format

Use the current recommended payload format for new integrations and record the schema contract. Treat string identifier changes and renamed event fields as a versioned migration.

Step 2: Create the hook