create, list, and update punch list items on a procore project via the rest api
domain: developers.procore.com · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Authenticate via OAuth 2.0 and obtain an access token scoped to the target Procore company/project.
Use the Punch Items reference (developers.procore.com/reference/rest/punch-items) to list existing punch items for a given project.
Check the Punch List filter-options and available manager/assignee-options endpoints to build valid filter and assignment values before writing.
Create a new punch item against the project, supplying required fields such as title, status, location, and assignee as defined in the current reference schema.
Use Punch Item Assignments to add or update assignees on a punch item after creation.
Update punch item status/fields as work progresses, re-checking the live reference page for exact field names since Procore versions its REST API (v1.0/v1.1 coexist).
Known gotchas
Procore's reference pages are JS-rendered and versioned — hardcode paths only after confirming them on the live reference page, since older tutorials may reflect a stale version.
Respect Procore's rate limit (documented default 3,600 requests/hour per app, 100 requests/10s spike limit) — bulk punch item sync jobs commonly hit this.
Punch item assignee/status values are project-configurable in Procore, so valid options must be fetched per-project via the filter/assignee-option endpoints rather than assumed static.
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?