Working with several workspaces

Each request acts on one workspace: your key’s default, or any other workspace you belong to, named with the workspace_id parameter.

Last checked against the API October 10, 2026 · View as Markdown

Posts, connected accounts and analytics belong to a workspace. Agencies usually keep one workspace per client, so the same key can manage every client’s calendar.

The default workspace

Without workspace_id, a request acts on the workspace your key was created in. GET /api/v1/workspace tells you which one that is.

Acting on another workspace

  1. Call GET /api/v1/workspaces to list every workspace you belong to.
  2. Pass the id you want as workspace_id: a query parameter on GET, PATCH and DELETE requests, or a body field when you create a post.
Scheduled posts in a client workspace
curl "https://studio.postprism.app/api/v1/posts?status=scheduled&workspace_id=7b2d4e6f-0000-4000-8000-00000000b002" \
  -H "Authorization: Bearer $POSTPRISM_API_KEY"

Connected accounts differ per workspace, so call GET /api/v1/platforms with the same workspace_id before you create a post there.

A workspace you do not belong to returns 404 with “Workspace not found, or you are not a member of it.” Postprism never falls back to your default workspace, so a post can’t land in the wrong client’s calendar.
PreviousAuthenticationNextDrafts and publishing