Agent skill · data analytics · jeremylongshore
apollo-common-errors
Diagnose and fix common Apollo.io API errors.
Why this skill is useful
Provides specific error handling patterns and API usage guidelines for Apollo.io that the AI wouldn't reliably generate on its own.
What it needs
Requires apollo account access. About 4k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Apollo Common Errors Overview Comprehensive guide to diagnosing and fixing Apollo.io API errors. Apollo uses x-api-key header authentication and the base URL https://api.apollo.io/api/v1/. Apollo distinguishes between master and standard API keys — many endpoints require master keys. Prerequisites Valid Apollo.io API credentials Node.js 18+ or Python 3.10+ Instructions Step 1: Identify the Error Category Step 2: Handle 401 — Invalid API Key Common 401 causes: 1. Using apikey query parameter instead of x-api-key header 2. Key was revoked or regenerated in the dashboard 3. Key has trailing whitespace (check with echo -n "$APOLLOAPIKEY" wc -c) Step 3: Handle 403 — Wrong Key Type Endpoints that require a master key: POST /contacts (create/update) POST /emailercampaigns/search (sequences) POST /emailercampaigns/{id}/addcontactids POST /opportunities (deals) POST /tasks (tasks) DELETE /contacts/{id} Step 4: Handle 429 — Rate Limiting Apollo uses fixed-window rate limiting per endpoint category: Step 5: Handle 422 — Validation Errors Step 6: Build Comprehensive Error Middleware Error Reference Code Meaning Fix ------ --------- ----- 401 Invalid or missing x-api-key header Verify key in dashboard, check header name 403 Standard key used for master-only endpoint Generate master API key 422 Bad request body Check field names, perpage <= 100, page <= 500 429 Rate limit exceeded Read Retry-After header, implement backoff 500 Apollo server error Retry with backoff, check status.apollo.io ECONNREFUSED Network/firewall Allow outbound HTTPS to api.apollo.io:443 Output A classified error record containing the HTTP status, affected endpoint, and a redacted provider message suitable for the incident timeline A bounded recovery decision: rotate or correct credentials, request the required key type, retry within the server-provided window, or stop the job A reproducible diagnostic that uses a minimal request and never writes an Apollo key, raw contact data, or full request body to share …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/apollo-common-errors