From procore-pack
Handles Procore REST API errors (401, 429, 403) with Python OAuth2 auth examples, backoff strategies, and solutions for construction/project integrations.
How this skill is triggered — by the user, by Claude, or both
Slash command
/procore-pack:procore-common-errorsThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Implementation patterns for Procore common errors using the REST API with OAuth2 authentication.
Implementation patterns for Procore common errors using the REST API with OAuth2 authentication.
procore-install-auth setupimport 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())}")
| Error | Cause | Solution |
|---|---|---|
| 401 Unauthorized | Expired token | Re-authenticate |
| 429 Rate Limited | Too many requests | Implement backoff |
| 403 Forbidden | Insufficient permissions | Check project role |
See related Procore skills for more workflows.
5plugins reuse this skill
First indexed Jul 10, 2026
npx claudepluginhub fleet-to-force/claude-code-plugins-plus --plugin procore-packProvides patterns for handling common Procore API errors (401, 429, 403) with OAuth2 authentication. Use when integrating with construction management endpoints for project management, RFIs, or submittals.
Guides collaborative design exploration before implementation: explores context, asks clarifying questions, proposes approaches, and writes a design doc for user approval.
Creates structured, bite-sized implementation plans from specs or requirements before writing code. Useful for breaking down multi-step tasks into testable steps with file structure and task boundaries.