Noticed you’re on an iOS device.
Get our mobile app for effortless planning on the go.
Log in with planable.io
Noticed you’re on an Android device. Get our mobile app for effortless planning on the go.
Log in with planable.io
Planable is the best client-facing social media tool we've ever used and we've used a lot.
I’ve led social media teams at Oracle and Uber, and now I am the CMO at Planable. Across every team size, one pattern keeps showing up: the social media approval process breaks as you scale. I've watched the same frustration surface in agencies, in-house teams, and...
Jun 15, 2026
As they grow, agencies get to a point where the coordination gap between Planable and the rest of their stack becomes a real cost. Content lives in your CMS, your internal tools, your AI pipelines, but getting it into Planable, in the right workspace, and with the right media, means someone has to do it by hand. The approval flow is already there. The bottleneck is everything upstream of it.
The Planable Public API exists to cut the manual labor. It’s a REST API that gives external tools and custom scripts direct, programmatic access to your Planable account. Your technical team can build the integration your workflow actually needs, not retrofit the one someone else built.
Think of it as issuing a set of keys to a trusted tool: you decide the scope of access, which workspaces it can touch, and how long the keys are valid. You can revoke them instantly if anything changes.
The API is versioned, all endpoints live under /api/v1, and comes with interactive docs at api.planable.io/api/v1/docs where your developer can explore every endpoint and run test requests directly.
The Planable Public API v1 covers the core data model. Here’s what’s available:
A few things worth knowing before you build:
Create
Schedule
Plan
Engage
Collaborate
Analyze
Approve
POST_ALREADY_PUBLISHED error.pageIds in a single create request and the API creates a grouped post, the same way Planable’s in-app CSV import works.For the full, always-current list of endpoints, parameters, and response shapes, the interactive reference at api.planable.io/api/v1/docs is authoritative. It also exposes the OpenAPI 3.1 spec as a downloadable file at /api/v1/openapi.json.
You need to be a company Owner or Administrator in Planable to create or manage API tokens. This isn’t a delegatable permission, it’s a security boundary.
pln_ and is always visible in the token list — but treat it like a password: anyone with the token can use the API on your behalf.Pro tip: Use the minimum scope your integration actually needs. If a tool only reads data, give it a Read-only token. If you only need it to touch one client workspace, restrict it to that workspace. Smaller scope = smaller blast radius if a token is ever mishandled.
Every Planable API token has two dimensions of access control: scope and workspace access.
Use the minimum scope your integration actually needs.
By default, a token has access to all company workspaces. When creating a token, you can restrict it to specific workspaces. This is worth doing for any integration that only needs to touch one or two clients.
Rate limits apply per token, enforced via a Redis-backed sliding window:
Every API response includes X-RateLimit-Limit, X-RateLimit-Remaining, and X-RateLimit-Reset headers so your developer can handle rate limits gracefully in code.
All token management lives in Company settings → API tokens. Every company Owner and Administrator can see and manage all company tokens — there’s no per-user token isolation.
From this view you can:
Each company can have up to 10 active tokens at a time. If you hit the limit, revoke one you no longer use before generating a new one.
Security note: API tokens are powerful — treat them like passwords. Never paste a token into a public document, a Slack message, or a Git repository. Store them in a password manager, use read-only scope whenever possible, and limit workspace access where you can. If you suspect a token has been exposed, revoke it immediately and generate a new one.
Most people generating tokens aren’t the ones writing the integration code. When you hand a token to a developer, give them:
pln_…)https://api.planable.io/api/v1The docs expose the full OpenAPI 3.1 spec at /api/v1/openapi.json, which imports directly into Postman, Insomnia, or any API client.
Authentication is Bearer token. Every request needs this header:
Authorization: Bearer pln_your_token_here
Error responses follow a consistent JSON shape:
{
"error": {
"code": "VALIDATION_ERROR",
"message": "workspaceId is required",
"details": []
}
}
Standard HTTP status codes apply: 401 for an invalid or expired token, 403 for a scope or workspace access violation, 429 for rate limit exceeded, 400 for validation errors, and 404 for resources that don’t exist.
Planable offers three ways to connect to other tools. They’re complementary and can all run simultaneously.
The Planable Public API is available on Pro and Enterprise plans only.
The MCP connector — which gives Claude, ChatGPT, and Gemini read/write access to your workspaces — is available on all plans including the free trial. If you want AI-assisted content creation rather than custom code integration, we prepared a guide for where to start.
The Planable Public API is a REST API that gives external tools and scripts direct access to your Planable account. Using token-based authentication, it lets you read workspace and post data, create and update content, manage media, and more, without logging into the Planable app. All endpoints are at api.planable.io/api/v1.
Only company Owners and Administrators can create, view, and revoke API tokens. The token management UI is in Company Settings, which is not accessible to Editors, Contributors, Writers, or Approvers.
The Planable Public API is available on Pro and Enterprise plans. It is not available on the Basic plan. The MCP connector, a separate product, is available on all plans including free.
Yes. When creating a token, you can select All workspaces (the default) or restrict it to specific workspaces. Limiting a token to specific workspaces is recommended for integrations that only need to touch one or two clients.
No. Posts created via the API land as drafts in your workspace and follow the same approval settings as posts created in the Planable UI. If your workspace has auto-publish on approval enabled, a post created via API will publish once it’s approved, but nothing goes live without sign-off first.
No. Published posts are immutable in the Planable API. Attempting to update a published post returns a 400 error with code POST_ALREADY_PUBLISHED. You can only update posts that are still in draft or scheduled state.
If a workspace is deleted, it is automatically removed from any tokens that reference it. Tokens scoped to all workspaces are unaffected — the workspace simply no longer exists in scope. No tokens are revoked automatically.
No. Webhooks are not available in v1. To track changes in post status or approval state, your integration will need to poll the relevant endpoints. Webhooks are on the product roadmap.
Each Planable company can have up to 10 active (non-revoked) tokens at a time. To add a new one when at the limit, revoke a token you no longer use.
The Planable Public API enforces per-token rate limits: 600 requests per minute for read endpoints, 120 requests per minute for write endpoints. Rate limit headers (X-RateLimit-Limit, X-RateLimit-Remaining, X-RateLimit-Reset) are included in every response.
The Planable MCP connector lets AI tools like Claude, ChatGPT, and Gemini interact with your Planable workspaces directly through conversation. It requires no code. The Planable Public API is a REST API for developers building custom integrations and automation pipelines. MCP is available on all plans including free; the Public API requires a Pro or Enterprise plan.
Ready to build? Go to Profile settings → Integrations → Public API → Generate tokens, then hand your developer the base URL (https://api.planable.io/api/v1) and the interactive docs.