The PostEverywhere developer hub

The PostEverywhere API is a REST API that lets you programmatically schedule and publish social media posts across all top platforms (Instagram, X, LinkedIn, Facebook, TikTok, YouTube, Threads, Pinterest, Bluesky, Discord, Telegram, and WordPress), upload media, manage connected accounts, subscribe to webhooks, group posts into campaigns, and monitor publishing results, all from a single integration with 49 endpoints.

Open the Developers page in the PostEverywhere dashboard (under Manage in the sidebar) and create a key: name it, choose its permissions (Read, Write and/or AI) and copy it. It starts with pe_live_ and is shown only once, so store it securely.

Yes. API access is included on all PostEverywhere plans, from Lite ($9/mo) to Scale ($39/mo). There is no separate API add-on or enterprise-only gating. View full pricing.

The API supports all top platforms available in PostEverywhere: Instagram (posts, Reels, Stories, carousels), X (tweets, threads, articles), LinkedIn (profiles, company pages), Facebook (pages, Reels), TikTok (videos), YouTube (videos, Shorts), Threads (text, images), Pinterest (pins), Bluesky (posts), Discord (channels), Telegram (channels), and WordPress.

Yes. When creating a post via POST /posts, pass multiple account IDs in the account_ids array. The API publishes to all specified platforms simultaneously from a single request.

Subscribe to events with POST /webhooks, supplying a URL and an event list. We send signed JSON deliveries with an X-PostEverywhere-Signature header whose value is sha256= followed by the HMAC-SHA256 of the raw body, keyed with the secret returned at subscription time. 15 event types are supported, including post.published, post.failed, and account.reconnect_needed. Failed deliveries retry with exponential backoff. Each organisation can create up to 25 webhook subscriptions.

You can create up to 50 posts per call via POST /posts/bulk. Each post in the batch is validated independently and reports its own success or failure in the response, so partial batches are reported cleanly. Use this for content pipelines, CMS imports, and large editorial rollouts.

Yes, and you can connect to it two ways. The hosted server at https://mcp.posteverywhere.ai needs nothing installed (every tool is listed on the AI agents page): in Claude Code, run claude mcp add --transport http posteverywhere https://mcp.posteverywhere.ai --header "Authorization: Bearer pe_live_YOUR_KEY". Or run the open-source server @posteverywhere/mcp locally with npx -y @posteverywhere/mcp. Both expose 39 tools that Claude Code, Claude Desktop, Cursor, Cline, Windsurf, Zed, and any MCP-compatible AI coding agent can use directly to schedule posts, retry failures, or build webhook subscriptions in natural language. See the setup guide.

Yes. The Logs page in the dashboard lists every call made with an API key, including MCP tool calls from Claude, ChatGPT and Cursor, with the status, action, who made it, duration, error and redacted request and response bodies. Every response carries an X-Request-Id header you can search for. Logs are kept for 30 days on every plan. See the logs guide.

Yes. POST /posts/retry-failed retries failed destinations by filter (platform, account, time window). Use this after fixing a token issue, restoring an account, or recovering from a platform outage, rather than retrying posts one at a time. For a single post, POST /posts/{id}/retry retries only the failed destinations.

GET /me returns the API key context in one call: the organisation, the plan tier, current quota usage (posts, AI credits, accounts), the scopes granted to the key, and feature flags. SDKs use this to self-configure without hardcoded IDs, and white-label tools use it to render plan-aware UI.

API requests are rate-limited to 60 requests per minute and 1,000 per hour per API key. Rate limit headers (X-RateLimit-Limit, X-RateLimit-Remaining, X-RateLimit-Reset, Retry-After) are included in every response.

We provide an official Node.js SDK on npm (npm install @posteverywhere/sdk, source on GitHub) and an MCP server (@posteverywhere/mcp, source on GitHub) that works with any MCP-compatible AI coding agent, Claude Code, Cursor, Codex CLI, Windsurf, Cline, Zed, and more. We also publish code examples in cURL. The API follows REST conventions and works with any HTTP client in any language.

Yes. Install @posteverywhere/cli with npm install -g @posteverywhere/cli and post or schedule across all top platforms straight from your terminal. Run posteverywhere login once (a device-grant flow, like the GitHub CLI), then posteverywhere connect instagram and posteverywhere post -c "Launch day" -a 123. Every command also takes --json, so the CLI doubles as a tool your AI agents (Claude, Cursor) can call directly. Full command reference on the CLI page.

Currently, the API operates in production mode. We recommend creating a test organisation with sandbox social accounts for development. All API keys can be revoked instantly from the Developers page if needed.

Yes. You can use the PostEverywhere API to build a custom-branded scheduling tool for your clients. The API handles all platform authentication, media processing, and publishing, you build the UI. GET /me makes plan-aware rendering trivial. See our agency solutions for more details.

Send a POST request to /ai/generate-image with a text prompt. The API uses our AI image generator to create visuals and saves them to your media library. Pair it with the AI content generator (or call /ai/generate-caption for platform-tuned text) for fully automated posts. Each generation uses AI credits from your plan, and the cost depends on the model you pick.

Yes. Use the POST /posts endpoint to auto-publish content whenever your CMS publishes. Common integrations include WordPress webhooks, Ghost, and Contentful. You can also use RSS-to-post workflows with tools like n8n or Zapier connected to our API, and the integrations page has the exact HTTP block for each. Subscribe to post.published webhooks to close the loop in your CMS. Learn more about social media automation.

The API publishes to each platform independently. If Instagram succeeds but TikTok fails (e.g., token expired), you get per-platform results showing exactly which destinations succeeded and which failed. Use POST /posts/{id}/retry to retry only the failed destinations without re-publishing to platforms that already succeeded, or POST /posts/retry-failed for bulk recovery by filter.

No. Webhooks, campaigns, bulk operations and the MCP server were all added without breaking changes. Every existing integration keeps working without modification, and new capabilities are additive and opt-in.