Publora

Publora Workspace API

Manage multiple users (requires Workspace access - contact support)

Documentation GitHub OpenAPI

Operations 6

GET /workspace/users List managed users #

POST /workspace/users Create a managed user #

POST /workspace/users/attach Attach an existing user #

DELETE /workspace/users/{userId} Detach a managed user #

POST /workspace/users/{userId}/api-key Generate API key for managed user #

POST /workspace/users/{userId}/connection-url Get connection URL for managed user #

Work with this as data

Every API here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for apis

7 MCP tools reach this

find_apisBrowse and filter every API in the catalog.
get_api_artifactsOne API's artifacts, grouped by type.
get_openapiThe primary OpenAPI for this API.
find_similar_apisAPIs that look like this one.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.

All 92 tools →

Call it yourself

curl for this page

This API

curl "https://apis.io/api/v1/apis/publora-workspace-api"

All apis

curl "https://apis.io/api/v1/apis?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.

OpenAPI Specification

openapi: 3.2.0
info:
  title: Publora Workspace API
  description: 'Affordable REST API for scheduling and publishing social media posts

    across X/Twitter, LinkedIn, Instagram, Threads, TikTok, YouTube,

    Facebook, Bluesky, Mastodon, and Telegram.


    All plans include full API access. Starting at $5.40/month (yearly) or $9/month.

    14-day free trial, no credit card needed.


    ## Workspace API

    The Workspace API allows you to manage multiple users under a single account.

    **To enable Workspace access, please contact Publora support at serge@publora.com.**'
  version: 1.0.0
  contact:
    email: serge@publora.com
    url: https://publora.com
servers:
- url: https://api.publora.com/api/v1
  description: Production
security:
- ApiKeyAuth: []
tags:
- name: Workspace
  description: Manage multiple users (requires Workspace access - contact support)
paths:
  /workspace/users:
    parameters:
    - $ref: '#/components/parameters/XPubloraClient'
    get:
      summary: List managed users
      description: 'Retrieve all users managed under your workspace.


        **Requires Workspace access - contact serge@publora.com to enable.**'
      operationId: getManagedUsers
      tags:
      - Workspace
      responses:
        '200':
          description: List of managed users
          content:
            application/json:
              schema:
                type: object
                properties:
                  users:
                    type: array
                    items:
                      $ref: '#/components/schemas/ManagedUser'
        '403':
          description: Workspace access not enabled
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
              example:
                error: Workspace access is not enabled for this key
        '500':
          description: Server error
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
    post:
      summary: Create a managed user
      description: 'Create a new managed user under your workspace.

        The user can then connect their social accounts via a connection URL.


        **Requires Workspace access - contact serge@publora.com to enable.**'
      operationId: createManagedUser
      tags:
      - Workspace
      requestBody:
        required: true
        content:
          application/json:
            schema:
              type: object
              required:
              - username
              properties:
                username:
                  type: string
                  format: email
                  description: User's email address (must be unique)
                  example: user@example.com
                displayName:
                  type: string
                  description: Display name (defaults to email if not provided)
                  example: John Doe
      responses:
        '201':
          description: User created
          content:
            application/json:
              schema:
                type: object
                properties:
                  user:
                    $ref: '#/components/schemas/ManagedUser'
        '400':
          description: Missing required fields
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
              example:
                error: Email is required
        '403':
          description: Workspace access not enabled
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
        '409':
          description: 'An account with this email already exists. The response includes

            `userId` and membership fields (`attachable`, `requiresConsent`,

            `reason`, `alreadyInWorkspace`, `managedByAnotherWorkspace`). When

            `attachable: true`, attach the user via POST /workspace/users/attach.

            '
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
              example:
                error: User with this email already exists
                code: email_exists
                userId: 6626a1f5e4b0c91a2d3f4567
                alreadyInWorkspace: false
                managedByAnotherWorkspace: false
                reason: standalone_user_exists
                attachable: true
                requiresConsent: true
        '500':
          description: Server error
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
  /workspace/users/attach:
    parameters:
    - $ref: '#/components/parameters/XPubloraClient'
    post:
      summary: Attach an existing user
      description: 'Attach an existing standalone Publora user to your workspace as a managed

        user. Because the target account already exists, this requires the target

        user''s consent: a valid access token belonging to that user (the

        `accessToken` returned when they sign in), passed as `userAccessToken`.

        Re-attaching a user who is already in your workspace is idempotent and

        does not require a consent token.


        **Requires Workspace access - contact serge@publora.com to enable.**'
      operationId: attachManagedUser
      tags:
      - Workspace
      requestBody:
        required: true
        content:
          application/json:
            schema:
              type: object
              properties:
                email:
                  type: string
                  format: email
                  description: The existing user's email. Provide either email or userId (also accepted as `username`).
                  example: user@example.com
                userId:
                  type: string
                  description: The existing user's ObjectId. Provide either email or userId.
                  example: 6626a1f5e4b0c91a2d3f4567
                userAccessToken:
                  type: string
                  description: The target user's access token, proving consent. Required unless the user is already in your workspace. Also accepted as `attachToken` in the body or via the `x-publora-user-token` header.
              example:
                email: user@example.com
                userAccessToken: eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9...
      responses:
        '200':
          description: User attached (or already in your workspace)
          content:
            application/json:
              schema:
                type: object
                properties:
                  user:
                    $ref: '#/components/schemas/ManagedUser'
                  alreadyInWorkspace:
                    type: boolean
                    description: true if the user was already managed by your workspace (idempotent re-attach)
                    example: false
        '400':
          description: Missing/invalid identifier, mismatched email vs userId, or the owner's own account
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
              example:
                error: Email or userId is required
                code: missing_identifier
        '403':
          description: Workspace access not enabled, the target user's consent token is missing/invalid/mismatched, or attaching would exceed the plan's connection limit
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
              example:
                error: Target user consent token is required
                code: attach_consent_required
        '404':
          description: No active user matches the identifier
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
              example:
                error: User not found
                code: user_not_found
        '409':
          description: The target user is inactive, a workspace owner, in another workspace, or has an active subscription
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
              example:
                error: Cannot attach a user with an active subscription
                code: user_has_active_subscription
        '500':
          description: Server error
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
  /workspace/users/{userId}:
    parameters:
    - $ref: '#/components/parameters/XPubloraClient'
    delete:
      summary: Detach a managed user
      description: 'Remove a user from your workspace. The user account is not deleted,

        but is no longer managed by your workspace.


        **Requires Workspace access - contact serge@publora.com to enable.**'
      operationId: detachManagedUser
      tags:
      - Workspace
      parameters:
      - name: userId
        in: path
        required: true
        schema:
          type: string
        example: 507f1f77bcf86cd799439011
      responses:
        '200':
          description: User detached
          content:
            application/json:
              schema:
                type: object
                properties:
                  success:
                    type: boolean
                    example: true
        '400':
          description: Invalid userId
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
        '403':
          description: Workspace access not enabled
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
        '404':
          description: User not found or not managed by this key
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
        '500':
          description: Server error
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
  /workspace/users/{userId}/api-key:
    parameters:
    - $ref: '#/components/parameters/XPubloraClient'
    post:
      summary: Generate API key for managed user
      description: 'Generate a new API key for a managed user. This key can be used

        to make API calls on behalf of the managed user (e.g., create posts

        to their connected social accounts).


        **Requires Workspace access - contact serge@publora.com to enable.**'
      operationId: generateManagedUserApiKey
      tags:
      - Workspace
      parameters:
      - name: userId
        in: path
        required: true
        schema:
          type: string
      responses:
        '200':
          description: API key generated
          content:
            application/json:
              schema:
                type: object
                properties:
                  message:
                    type: string
                    example: API key generated successfully
                  apiKey:
                    type: string
                    description: The generated API key (save it securely - shown only once)
                    example: sk_lx5abc.a1b2c3d4e5f6...
                  userId:
                    type: string
        '400':
          description: Invalid userId
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
        '403':
          description: Workspace or API access not enabled
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
              examples:
                noWorkspace:
                  value:
                    error: Workspace access is not enabled for this key
                noApiAccess:
                  value:
                    error: API access is not enabled for this workspace owner
        '404':
          description: User not found or not managed by this key
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
        '500':
          description: Server error
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
  /workspace/users/{userId}/connection-url:
    parameters:
    - $ref: '#/components/parameters/XPubloraClient'
    post:
      summary: Get connection URL for managed user
      description: 'Get or generate a URL that allows a managed user to connect their

        social media accounts. The URL expires after a configurable period

        (default: 90 days).


        **Requires Workspace access - contact serge@publora.com to enable.**'
      operationId: getConnectionUrl
      tags:
      - Workspace
      parameters:
      - name: userId
        in: path
        required: true
        schema:
          type: string
      requestBody:
        required: false
        content:
          application/json:
            schema:
              type: object
              properties:
                rotate:
                  type: boolean
                  description: Force generation of a new token even if current is valid
                  default: false
                expiresInDays:
                  type: integer
                  description: Number of days until the token expires
                  default: 90
                  example: 30
      responses:
        '200':
          description: Connection URL
          content:
            application/json:
              schema:
                type: object
                properties:
                  url:
                    type: string
                    format: uri
                    description: URL for user to connect their social accounts
                    example: https://app.publora.com/connect/abc123...
                  tokenExpiresAt:
                    type: string
                    format: date-time
                    description: When the connection URL expires
        '400':
          description: Invalid userId
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
        '403':
          description: Workspace access not enabled
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
        '404':
          description: User not found or not managed by this key
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
        '500':
          description: Server error
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
components:
  parameters:
    XPubloraClient:
      name: x-publora-client
      in: header
      required: false
      description: Optional client identifier accepted by every API-key-authenticated operation. Any non-empty value is preserved; `api` is used when absent. Setting `mcp` triggers the MCP access entitlement check.
      schema:
        type: string
  schemas:
    ManagedUser:
      type: object
      properties:
        _id:
          type: string
          description: User ID
          example: 507f1f77bcf86cd799439011
        username:
          type: string
          description: User email
          example: user@example.com
        displayName:
          type: string
          example: John Doe
        role:
          type: string
          enum:
          - managed
          example: managed
        dailyPostsLeft:
          type: integer
          example: 100
        connectionsPageUrl:
          type:
          - string
          - 'null'
          format: uri
          description: URL for user to connect their social accounts
        connectionsPageTokenExpiresAt:
          type:
          - string
          - 'null'
          format: date-time
    Error:
      type: object
      properties:
        error:
          type: string
          description: Human-readable message. Do not match on this string — match on code where present.
          example: Invalid API key
        code:
          type: string
          description: 'Stable machine-readable error code. Present on the newer error paths

            (scheduling, platformSettings validation, idempotency); older errors

            return `error` only. Always prefer this over the `error` text.

            '
          example: SCHEDULED_TIME_IN_PAST
        field:
          type: string
          description: '`PLATFORM_SETTING_UNKNOWN` only. The exact dotted path of the rejected

            key, relative to the `platformSettings` object (no `platformSettings.`

            prefix).

            '
          example: youtube.thumbnail.typo
        serverTime:
          type: string
          format: date-time
          description: '`SCHEDULED_TIME_IN_PAST` only. Current server time (UTC) when the

            request was rejected — compare against your clock to diagnose skew.

            '
          example: '2026-03-01T14:02:11.412Z'
  securitySchemes:
    ApiKeyAuth:
      type: apiKey
      in: header
      name: x-publora-key
      description: 'API key from Settings > API Keys. Format: sk_timestamp.hexstring'