Skip to main content
Beyond HTTP status codes, Postsiva returns structured 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 platform
  • GET /unified/analytics — platform omitted from totals
  • Multi-platform post results[]success: false
Fix:
Bluesky requires 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:
Fix: Upgrade plan at postsiva.com or reduce usage.

Invalid API key

Fix:
  1. Confirm key starts with psk_live_
  2. Copy full key from Settings (shown once at creation)
  3. Revoke compromised keys and create new ones
MCP returns plain text in tool results:

Scope mismatch

API key scope restricts which platforms can be accessed.
HTTP status: 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

HTTP errors

Status codes

Authentication

Scopes and plan table

Errors overview

Two-layer model