> ## Documentation Index
> Fetch the complete documentation index at: https://docs.postlybee.com/llms.txt
> Use this file to discover all available pages before exploring further.

# PostlyBee Public API

> Create posts, upload media, discover connected accounts, and automate social publishing.

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.

<Tip>
  New here? Follow the [Quickstart](/quickstart) to authenticate, list connected
  accounts, and schedule your first post.
</Tip>

## Start here

<CardGroup cols={3}>
  <Card title="Quickstart" icon="rocket" href="/quickstart">
    Make your first authenticated request and schedule a post.
  </Card>

  <Card title="Authentication" icon="key" href="/essentials/authentication">
    Send your workspace API key as a Bearer token.
  </Card>

  <Card title="API reference" icon="braces" href="/api-reference/overview">
    Explore every endpoint with an interactive playground.
  </Card>
</CardGroup>

## Base URL

All REST endpoints use the following production origin:

```text theme={null}
https://api.postlybee.com
```

Version 1 endpoints begin with `/public/v1`. PostlyBee uses HTTPS only in production.

## What you can build

<CardGroup cols={2}>
  <Card title="Publishing workflows" icon="calendar-clock">
    Create drafts, schedule posts, publish immediately, or build threads for
    connected accounts.
  </Card>

  <Card title="Media pipelines" icon="image">
    Upload images and video files before attaching them to a post.
  </Card>

  <Card title="Account discovery" icon="users">
    List connected social accounts and select the correct destination by ID.
  </Card>

  <Card title="Agent integrations" icon="bot" href="/mcp/overview">
    Connect compatible AI clients through PostlyBee's OAuth-enabled MCP server.
  </Card>
</CardGroup>

## Request flow

Most publishing integrations follow the same sequence:

1. Read the API key from a secure secret store.
2. List connected accounts and select an account ID.
3. Upload any media and keep the returned media ID and URL.
4. Create a draft, scheduled post, or immediate post.
5. Query the post later to inspect its state and publication URL.

<Warning>
  API keys grant access to a workspace. Never expose them in browser code,
  public repositories, query strings, or client-side logs.
</Warning>

## Rate limits

Posts and upload endpoints are limited to **100 requests per workspace in a one-hour window**. Other public endpoints are currently not throttled by this limit. See [Rate limits](/essentials/rate-limits) for response headers and retry behavior.