For the complete documentation index, see llms.txt. This page is also available as Markdown.

Workspaces

Manage organizational units (“workspaces”) that group social accounts, members, and content. Workspaces help agencies, brands, and departments keep clients and campaigns separate under a single Publer login.

Requirements

  • Authentication: Bearer API token

  • Scope: workspaces

  • Headers:

    • Authorization: Bearer-API YOUR_API_KEY

Endpoint

List Workspaces

Retrieve all workspaces accessible by the authenticated user.

GET /api/v1/workspaces

List Workspaces

get

Retrieves a list of all workspaces that the authenticated user has access to.

Authorizations
AuthorizationstringRequired

API key authentication. Format: "Bearer-API YOUR_API_KEY"

Responses
200

Successful operation

application/json
idstringOptional

Unique identifier for the workspace

Example: 61a7c2e4f9e8c3b2d1e0f9a8
namestringOptional

The workspace's display name

Example: Marketing Team
membersobject[]Optional

List of users with access to the workspace

planstringOptional

Subscription plan of the workspace

Example: business
picturestringOptional

URL to the workspace's logo

Example: https://publer-dev.s3.amazonaws.com/uploads/logos/marketing_team_logo.png
get/workspaces

Working with Workspaces

  • A user can belong to multiple workspaces.

  • Each workspace has its own accounts, posts, and settings.

  • Use the workspace context (Publer-Workspace-Id header) to target API calls at the correct workspace.

Workspace Context for Other Endpoints

Many endpoints require you to specify which workspace you’re operating in. Include the Publer-Workspace-Id header:

  • Users API - Access user profile information

  • Accounts API - Access social accounts within workspaces

  • Posts API — Create, schedule, and manage content

Last updated

Was this helpful?