401 — the API key was rejected
401 — the API key was rejected
The key was rotated, or copied with surrounding whitespace. Re-copy it from Settings → Integrations. In a Claude connector, disconnect and reconnect. Confirm the key is a UUID.
403 — that operation is not available
403 — that operation is not available
You asked for something outside the API key’s scope — billing, agency administration, tenant configuration or team management. These are only available in the web app.
A campaign will not launch
A campaign will not launch
Run campaign_get. Its _readiness block lists every blocker — usually no sequence, no lead source, no sending account, or a CSV still processing.
An AI step fails
An AI step fails
GPT, QUALIFIER and CUSTOM AI Decision Maker each need a connected AI provider (OPENAI, ANTHROPIC, GEMINI, GROK or DEEPSEEK). A QUALIFIER step also needs a personaId.
The campaign is active but nothing is sending
The campaign is active but nothing is sending
Check linkedin_account_get: isValid:false means disconnected, isPaused means stopped, weeklyLimitReached means LinkedIn’s invitation ceiling was hit. Also check schedule and holidays.
A Pro-only step is refused
A Pro-only step is refused
EMAIL, QUALIFIER, GPT, FINDER and EVENT steps need a Pro or Agency plan, as do the If_Interested and CUSTOM branch conditions and ENGAGEMENT’s commentsToAdd. A QUALIFIER step also needs the Personas permission. Call whoami — _derived lists what is locked. The refusal comes from your plan, so rephrasing will not help.