From podium-pack
Provides patterns for handling common Podium API errors (401, 429, 403) with OAuth2 auth in messaging, reviews, and payments integrations.
How this skill is triggered — by the user, by Claude, or both
Slash command
/podium-pack:podium-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 Podium common errors using the REST API with OAuth2 authentication.
Implementation patterns for Podium common errors using the REST API with OAuth2 authentication.
podium-install-auth setupimport axios from 'axios';
const podium = axios.create({
baseURL: 'https://api.podium.com/v4',
headers: { 'Authorization': `Bearer ${process.env.PODIUM_ACCESS_TOKEN}` },
});
const { data } = await podium.get('/locations');
console.log(`Locations: ${data.data.length}`);
| Error | Cause | Solution |
|---|---|---|
| 401 Unauthorized | Expired token | Refresh OAuth token |
| 429 Rate Limited | Too many requests | Implement backoff |
| 403 Forbidden | Missing scope | Update OAuth app scopes |
See related Podium skills for more workflows.
npx claudepluginhub fleet-to-force/claude-code-plugins-plus --plugin podium-pack4plugins reuse this skill
First indexed Jul 10, 2026
Hardens production Podium OAuth2 integrations against access-token expiry storms, refresh-token decay, scope drift, secret leakage, multi-tenant routing failures, and credential rotation downtime.
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.