Skip to main content
The PostlyBee Public API lets your application publish content through the social accounts already connected to a PostlyBee workspace. Use it for internal tools, workflow automation, content pipelines, or product integrations.
New here? Follow the Quickstart to authenticate, list connected accounts, and schedule your first post.

​
Start here

Quickstart

Make your first authenticated request and schedule a post.

Authentication

Create a scoped user API token and restrict its workspace access.

API reference

Explore every endpoint with an interactive playground.

​
Base URL

All REST endpoints use the following production origin:
Version 1 endpoints begin with /public/v1. PostlyBee uses HTTPS only in production.

​
What you can build

Publishing workflows

Create drafts, schedule posts, publish immediately, or build threads for connected accounts.

Media pipelines

Upload images and video files before attaching them to a post.

Account discovery

Connect accounts and inspect provider settings and tools.

Analytics and notifications

Read account and post metrics and monitor workspace notifications.

CLI automation

Run Workspace-scoped API workflows from terminals, CI jobs, and agents.

Agent integrations

Connect compatible AI clients through PostlyBee’s OAuth-enabled MCP server.

​
Request flow

Most publishing integrations follow the same sequence:
  1. Read the API token from a secure secret store.
  2. List available workspaces and select a workspace ID.
  3. List that workspace’s connected accounts and select an account ID.
  4. Upload any media and keep the returned media ID and URL.
  5. Create a draft, scheduled post, or immediate post.
  6. Query the post later to inspect its state and publication URL.
API tokens may grant access to several workspaces. Never expose them in browser code, public repositories, query strings, or client-side logs.

​
Rate limits

Workspace resource endpoints share a limit of 100 requests per workspace in a one-hour window. Workspace discovery is limited per token. See Rate limits for response headers and retry behavior.
Last modified on August 26, 2026