error fields in response bodies — especially for multi-platform operations and connection checks.
NOT_CONNECTED
Platform account is not linked to the workspace.
Where it appears:
GET /unified/posts— empty slice for disconnected platformGET /unified/analytics— platform omitted from totals- Multi-platform post
results[]—success: false
handle + app_password — see Bluesky.
Plan blocked (plan_required)
Feature or credit not available on the workspace owner’s plan.
Common feature gates
HTTP status:
403 Forbidden
Credit exhaustion uses 402 Payment Required:
Invalid API key
Fix:
- Confirm key starts with
psk_live_ - Copy full key from Settings (shown once at creation)
- Revoke compromised keys and create new ones
Scope mismatch
API keyscope restricts which platforms can be accessed.
403 Forbidden
Scope examples
Fix: Create a new key with appropriate scope in Settings → API Keys.
OAuth connect, post, and read endpoints all enforce scope.
Platform-specific errors
These appear in post
results[] with success: false.
Handling in code
Related
HTTP errors
Status codes
Authentication
Scopes and plan table
Errors overview
Two-layer model