salesloft-common-errors
Diagnose and fix SalesLoft API errors: 401, 403, 422, 429, and 5xx. Use when encountering SalesLoft errors, debugging failed requests, or troubleshooting OAuth token issues. Trigger: "salesloft error", "fix salesloft", "salesloft not working", "salesloft 429".
Best use case
salesloft-common-errors is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Diagnose and fix SalesLoft API errors: 401, 403, 422, 429, and 5xx. Use when encountering SalesLoft errors, debugging failed requests, or troubleshooting OAuth token issues. Trigger: "salesloft error", "fix salesloft", "salesloft not working", "salesloft 429".
Teams using salesloft-common-errors should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/salesloft-common-errors/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How salesloft-common-errors Compares
| Feature / Agent | salesloft-common-errors | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Diagnose and fix SalesLoft API errors: 401, 403, 422, 429, and 5xx. Use when encountering SalesLoft errors, debugging failed requests, or troubleshooting OAuth token issues. Trigger: "salesloft error", "fix salesloft", "salesloft not working", "salesloft 429".
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
Related Guides
AI Agents for Marketing
Discover AI agents for marketing workflows, from SEO and content production to campaign research, outreach, and analytics.
AI Agents for Coding
Browse AI agent skills for coding, debugging, testing, refactoring, code review, and developer workflows across Claude, Cursor, and Codex.
Best AI Agents for Marketing
A curated list of the best AI agents and skills for marketing teams focused on SEO, content systems, outreach, and campaign execution.
SKILL.md Source
# SalesLoft Common Errors
## Overview
Quick reference for the most common SalesLoft REST API v2 errors. All errors return JSON with a message field. Rate limiting uses a cost-based system (600 cost/minute).
## Error Reference
### 401 Unauthorized -- Invalid or Expired Token
```json
{ "error": "Not authorized", "error_description": "The access token is invalid" }
```
**Causes:** Token expired, revoked, or wrong environment key.
**Fix:**
```typescript
// Check if token works
const { data } = await api.get('/me.json').catch(err => {
if (err.response?.status === 401) {
console.error('Token invalid. Refreshing...');
return refreshAccessToken(storedRefreshToken);
}
throw err;
});
```
### 403 Forbidden -- Insufficient Scopes
```json
{ "error": "Forbidden", "error_description": "Insufficient scope for this resource" }
```
**Fix:** Check app scopes in [developer portal](https://developers.salesloft.com). Common issue: using user-level OAuth for team-level endpoints (cadences, team templates).
### 404 Not Found -- Wrong Endpoint or Deleted Resource
```bash
# Verify endpoint format -- all endpoints end with .json
curl -s -H "Authorization: Bearer $TOKEN" \
https://api.salesloft.com/v2/people/12345.json
# NOT /people/12345 (missing .json suffix)
```
### 422 Unprocessable Entity -- Validation Errors
```json
{
"errors": [
{ "attribute": "email_address", "message": "is required" },
{ "attribute": "email_address", "message": "has already been taken" }
]
}
```
**Common 422 causes:**
| Field | Error | Solution |
|-------|-------|----------|
| `email_address` | required | Must include when creating a person |
| `email_address` | already taken | Use `GET /people.json?email_addresses[]=x` first |
| `cadence_id` | not active | Cadence must have `current_state: 'active'` |
| `person_id` | already enrolled | Check existing cadence memberships |
### 429 Too Many Requests -- Rate Limit Exceeded
```
X-RateLimit-Limit-Per-Minute: 600
X-RateLimit-Remaining-Per-Minute: 0
Retry-After: 42
```
**SalesLoft uses cost-based rate limiting:**
- Default: each request costs 1 point
- Pages 101-150: 3 points per request
- Pages 151-250: 8 points per request
- Pages 251-500: 10 points per request
- Pages 501+: 30 points per request
```typescript
// Auto-retry with Retry-After header
api.interceptors.response.use(undefined, async (error) => {
if (error.response?.status === 429) {
const wait = parseInt(error.response.headers['retry-after'] || '60');
await new Promise(r => setTimeout(r, wait * 1000));
return api.request(error.config);
}
throw error;
});
```
### 5xx Server Errors
**Fix:** Retry with exponential backoff. Check [status.salesloft.com](https://status.salesloft.com) for outages.
## Quick Diagnostic
```bash
# 1. Verify token
curl -s -H "Authorization: Bearer $SALESLOFT_API_KEY" \
https://api.salesloft.com/v2/me.json | jq '.data.email'
# 2. Check API status
curl -s https://status.salesloft.com/api/v2/status.json | jq '.status'
# 3. Test specific endpoint
curl -v -H "Authorization: Bearer $SALESLOFT_API_KEY" \
'https://api.salesloft.com/v2/people.json?per_page=1'
# 4. Check rate limit remaining
curl -sI -H "Authorization: Bearer $SALESLOFT_API_KEY" \
https://api.salesloft.com/v2/people.json | grep -i ratelimit
```
## Error Handling
| Status | Retryable | Action |
|--------|-----------|--------|
| 401 | No | Refresh token or re-authenticate |
| 403 | No | Update app scopes in developer portal |
| 404 | No | Check endpoint URL (must end in `.json`) |
| 422 | No | Fix request payload |
| 429 | Yes | Wait for `Retry-After` header value |
| 500-503 | Yes | Exponential backoff, check status page |
## Resources
- [SalesLoft API Basics](https://developers.salesloft.com/docs/platform/api-basics/)
- [Rate Limits](https://developers.salesloft.com/docs/platform/api-basics/rate-limits/)
- [Status Page](https://status.salesloft.com)
## Next Steps
For comprehensive debugging, see `salesloft-debug-bundle`.Related Skills
workhuman-common-errors
Workhuman common errors for employee recognition and rewards API. Use when integrating Workhuman Social Recognition, or building recognition workflows with HRIS systems. Trigger: "workhuman common errors".
wispr-common-errors
Wispr Flow common errors for voice-to-text API integration. Use when integrating Wispr Flow dictation, WebSocket streaming, or building voice-powered applications. Trigger: "wispr common errors".
windsurf-common-errors
Diagnose and fix common Windsurf IDE and Cascade errors. Use when Cascade stops working, Supercomplete fails, indexing hangs, or encountering Windsurf-specific issues. Trigger with phrases like "windsurf error", "fix windsurf", "windsurf not working", "cascade broken", "windsurf slow".
webflow-common-errors
Diagnose and fix Webflow Data API v2 errors — 400, 401, 403, 404, 409, 429, 500. Use when encountering Webflow API errors, debugging failed requests, or troubleshooting integration issues. Trigger with phrases like "webflow error", "fix webflow", "webflow not working", "debug webflow", "webflow 429", "webflow 401".
vercel-common-errors
Diagnose and fix common Vercel deployment and function errors. Use when encountering Vercel errors, debugging failed deployments, or troubleshooting serverless function issues. Trigger with phrases like "vercel error", "fix vercel", "vercel not working", "debug vercel", "vercel 500", "vercel build failed".
veeva-common-errors
Veeva Vault common errors for REST API and clinical operations. Use when working with Veeva Vault document management and CRM. Trigger: "veeva common errors".
vastai-common-errors
Diagnose and fix Vast.ai common errors and exceptions. Use when encountering Vast.ai errors, debugging failed instances, or troubleshooting GPU rental issues. Trigger with phrases like "vastai error", "fix vastai", "vastai not working", "debug vastai", "vastai instance failed".
twinmind-common-errors
Diagnose and fix TwinMind common errors and exceptions. Use when encountering transcription errors, debugging failed requests, or troubleshooting integration issues. Trigger with phrases like "twinmind error", "fix twinmind", "twinmind not working", "debug twinmind", "transcription failed".
together-common-errors
Together AI common errors for inference, fine-tuning, and model deployment. Use when working with Together AI's OpenAI-compatible API. Trigger: "together common errors".
techsmith-common-errors
TechSmith common errors for Snagit COM API and Camtasia automation. Use when working with TechSmith screen capture and video editing automation. Trigger: "techsmith common errors".
supabase-common-errors
Diagnose and fix Supabase errors across PostgREST, PostgreSQL, Auth, Storage, and Realtime. Use when encountering error codes like PGRST301, 42501, 23505, or auth failures. Use when debugging failed queries, RLS policy violations, or HTTP 4xx/5xx responses. Trigger with "supabase error", "fix supabase", "PGRST", "supabase 403", "RLS not working", "supabase auth error", "unique constraint", "foreign key violation".
stackblitz-common-errors
Fix WebContainer and StackBlitz errors: COOP/COEP, SharedArrayBuffer, boot failures. Use when WebContainers fail to boot, embeds don't load, or processes crash inside WebContainers. Trigger: "stackblitz error", "webcontainer error", "SharedArrayBuffer not defined".