Social media API and CLI

One social media API for your coding agent.

Use the OpenPMM API or CLI from Claude Code, Codex, Amp, or your terminal to create, schedule, and publish Posts for your own accounts.

Sign up

Unified social media API

One contract for the accounts you already use.

The OpenPMM API gives your agent one way to work with connected social accounts. It keeps provider-specific authentication, destination state, and publishing details behind one public contract.

Create and manage a Workspace for your publishing workflow.
Connect each social account as a Destination and reuse it.
Keep provider credentials outside the content-generation context.
Return clear Post state, request IDs, and publication results.

Social media posting API

Create a Post, attach the media, and inspect the result.

Prepare a draft or direct Post with the destination, content, media, and timing it needs. The same Post remains the source of truth as it moves through preparation and publication.

Create a draft before a public action.
Attach images or videos through the Asset workflow.
Publish a reviewed Post with explicit confirmation.
Read accepted work until the Post is terminal or needs action.

Social media scheduler API

Publish now, schedule later, or use a queue.

The API supports direct publishing, exact scheduling, and queue-aware workflows. Your agent can choose the right timing without building a calendar system for every provider.

Send a Post immediately when the work is ready.
Set an explicit publication time and time zone.
Move queued Posts when the publishing plan changes.
Retry a failed Post without duplicating completed work.

Destinations and media

Keep platform rules behind the connection layer.

Every social platform handles accounts, media, limits, and errors differently. OpenPMM gives your workflow one Destination model and checks media against the selected channel before publishing.

Publish now to Bluesky, Facebook, Instagram, Mastodon, Threads, X, and YouTube.
Publish to TikTok now. LinkedIn is coming soon.
Validate media for one or more Destinations before the send.
Apply safe image changes when a technical conversion can fix the file.
Return a clear attention state when a human decision is required.

Social media CLI

Run the same API workflow from a terminal.

The first-party CLI is the terminal path through the same public API. Use it from a script, cron job, CI task, or coding agent that needs stable JSON output and predictable side effects.

List Workspaces and connected Destinations as JSON.
Upload Assets and create drafts from local files.
Publish from a request file and let the CLI own bounded status checks.
Run a read-only doctor check before deterministic automation.

Credential boundary

Keep CLI and direct API credentials separate.

The CLI credential store is an internal implementation detail. A CLI-managed agent invokes openpmm and never reads or exports its key. A custom /v1 client uses its own least-privilege credential from a secret manager.

Do not import the CLI key into an existing HTTP client.
Use request files and stable JSON for CLI-managed workflows.
Use separate credentials for direct API integrations and deployments.
Keep provider OAuth tokens behind the OpenPMM Destination layer.

Signed webhooks

Return Post events to the workflow that started them.

Create a Workspace webhook endpoint for signed Post events. Your automation can receive publication results without polling the API after every request.

Subscribe to events such as post.published and post.failed.
Verify the exact payload with the endpoint signing secret.
Test an endpoint before you connect it to production automation.
Rotate a signing secret when you need to replace it.

Confirmation boundary

Let the agent prepare the action without hiding it.

Publishing reaches a public account, so the final send stays explicit. Your agent can prepare the request, but a person reviews the Destination, content, media, and timing before the public side effect.

Complete OAuth yourself when you connect a Destination.
Require confirmation when an operation publishes or schedules.
Keep idempotency keys for safe retries after timeouts.
Use signed webhooks to return Post status to your workflow.

Product boundary

A publishing layer, not a white-label social suite.

OpenPMM is for individuals and small teams that want their own agent to publish to their own accounts. It is not a customer-facing API for embedding social publishing into another SaaS product.

Choose OpenPMM when your own agent is the primary operator.
Use a broader platform when you need inbox, listening, moderation, or enterprise reporting.
Keep campaign planning and brand rules in the agent skills that call the API.

Go deeper

Keep the workflow moving.

Explore the Social Media CLIRead the API quickstartSee the agent-native workflowCompare OpenPMM with other publishing tools

OpenPMM / sign up

Give your agent a publish button.

One focused workflow covers setup, scheduled posts, API and CLI access, and a clear confirmation boundary.

Sign up