Skip to main content
Every Postsiva account can belong to multiple workspaces. API keys are always workspace-scoped.

​
Model

When you call the API with psk_live_…, Postsiva resolves workspace_id from the key — you do not pass a workspace UUID unless you want to assert it matches.

​
What is scoped to a workspace

  • OAuth tokens per platform
  • Published and scheduled posts
  • Drafts
  • Comment sync and replies
  • Unified analytics aggregates
  • AI agent chat history (per workspace thread)
  • Media library uploads

​
Creating API keys

Requires workspace membership + Pro plan:
Response includes secret once, plus workspace_id, scope, and key_prefix. List and revoke via the same /workspaces/{id}/api-keys routes (JWT only — keys cannot manage themselves).

​
Multi-workspace users

If you belong to several workspaces, create one API key per workspace you automate. Each key only sees that workspace’s connected accounts and content.

​
JWT vs API key

Some routes (billing, workspace members, key management) require JWT and are not available with API keys alone.