| name | procore-migration-deep-dive |
| description | Procore migration deep dive — construction management platform integration.
Use when working with Procore API for project management, RFIs, or submittals.
Trigger with phrases like "procore migration deep dive", "procore-migration-deep-dive".
|
| allowed-tools | Read, Write, Edit, Bash(npm:*), Bash(pip:*), Bash(curl:*), Grep |
| version | 1.5.0 |
| license | MIT |
| author | Jeremy Longshore <jeremy@intentsolutions.io> |
| tags | ["saas","procore","construction","project-management"] |
| compatibility | Designed for Claude Code |
Procore Migration Deep Dive
Overview
Implementation patterns for Procore migration deep dive using the REST API with OAuth2 authentication.
Prerequisites
- Completed
procore-install-auth setup
Instructions
Step 1: API Call Pattern
import os, requests
token_resp = requests.post("https://login.procore.com/oauth/token", data={
"grant_type": "client_credentials",
"client_id": os.environ["PROCORE_CLIENT_ID"],
"client_secret": os.environ["PROCORE_CLIENT_SECRET"],
})
access_token = token_resp.json()["access_token"]
headers = {"Authorization": f"Bearer {access_token}"}
companies = requests.get("https://api.procore.com/rest/v1.0/companies", headers=headers)
print(f"Companies: {len(companies.json())}")
Output
- Procore API integration for migration deep dive
Error Handling
| Error | Cause | Solution |
|---|
| 401 Unauthorized | Expired token | Re-authenticate |
| 429 Rate Limited | Too many requests | Implement backoff |
| 403 Forbidden | Insufficient permissions | Check project role |
Resources
Next Steps
See related Procore skills for more workflows.
