Postly API is best when your app, backend, CMS, or automation is driving the publishing workflow.
Plan availability
API Access unlocks REST API and MCP access to capabilities included in your plan; it does not unlock Pro/Enterprise-only features. New activations retain their base plan limits for AI text, team members, and workspaces. Existing purchases with unlimited benefits retain those benefits. API keys and supported video upload benefits remain included.
What the API is designed for
- discovering accessible workspaces
- resolving connected publishing targets
- importing media from uploads, URLs, or base64
- creating drafts, scheduled posts, or recurring posts
- reading scheduled activity and analytics
- fitting governed publishing into a larger business system
The standard API shape
- Resolve the workspace.
- Fetch the connected targets or audience groups.
- Import or attach the media.
- Create or update the post.
- Schedule, publish, or store as draft.
- Read back activity or analytics as needed.
Where the API creates leverage
CMS and editorial systems
Turn approved content into scheduled social output without copy-pasting between tools.
Internal marketing tools
Let growth teams trigger publishing from launch systems, campaign builders, or reporting dashboards.
Automation platforms
Use Postly as the governed publishing layer behind low-code or no-code workflows.
AI-assisted apps
If your app generates content or media, the API can ingest it directly instead of requiring a separate hosting step first.
Important media note
One practical advantage of the API is media flexibility. It can accept:
- binary uploads
- public URLs
- base64 payloads
- data URLs
- inline media imports during create or update flows
That is especially useful for generated media or assets that already exist in memory.
If a workflow depends on temporary generated media, keep media ingestion and post creation in the same request flow. That reduces the chance of losing short-lived file references before the post is created.
When to choose MCP instead
Use MCP when an AI agent, not your app backend, is the actor that needs governed access to Postly capabilities.