Learn how to connect Planable to your internal tools, automation scripts, or custom workflows using the Planable Public API.
What is the Public API?
The Planable Public API lets you connect Planable to other tools you already use, like internal dashboards, custom scripts, or your team's automation pipeline. With it, you (or someone on your dev team) can pull data out of Planable, push new posts in, or trigger updates without anyone having to log into the app.
Think of it as giving a trusted tool a set of keys to your Planable account, but you decide which doors those keys open, and you can take them back at any time.
A few things you can do with it:
- Pull data into your tools — fetch your workspaces, pages, posts, media, or labels and use them anywhere (a dashboard, a spreadsheet, an internal report)
- Create posts automatically — draft and schedule posts straight from another system (a CMS, an approval workflow, a content database)
- Upload media in bulk — push a batch of images or videos into a workspace without uploading them one by one
- Keep analytics in sync — trigger a metrics refresh on a page or post when you need fresh numbers
How to generate an API token
You'll need to be a company Owner or Administrator to create or manage API tokens.
- Click your avatar in the top right corner and go to Account settings
- Open the Integrations tab
- Find the Public API card and click Generate tokens (or Manage tokens if you've already created some)
- You'll land in your Company settings, in the API tokens section. Fill in the form:
- Name — a label for your integration so you can recognize it later (e.g. Publishing Bot or Internal Dashboard)
-
Scopes — what this token is allowed to do:
- Read — fetch and view data only
- Write — create and update content (a Write token can also read)
- Workspaces — pick All workspaces or limit the token to specific ones
-
Expiry — choose how long the token should stay valid: 30 days, 60 days, 90 days, 6 months, 1 year, or Never
- Click Generate
- Copy the token right away and store it somewhere safe (a password manager works great). You'll be able to see it again in the list later, 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 want it to touch one workspace, restrict it to that workspace.
What the API can do
Here's a quick summary of what's available in v1. For the full, always-up-to-date list of endpoints and request examples, head to the interactive reference at api.planable.io/api/v1/docs.
| Area | What you can do |
|---|---|
| Workspaces | List, create, and delete workspaces |
| Pages | List connected pages, pull analytics, trigger a metrics sync |
| Posts | List, create, update unpublished posts, reorder, fetch analytics, manage comments |
| Media | List media and upload new media from a URL |
| Labels | List and create labels in a workspace |
| Stories | Create Instagram stories |
The API also enforces your usual plan and workspace permissions — a token can only do what the person who created it can do.
Sharing the token with your developer
Most non-technical users won't call the API themselves, you'll usually hand the token off to a developer or paste it into a tool's setup screen. When you do, share:
-
The token itself (starts with
pln_…) -
The base URL:
https://api.planable.io/api/v1 - A link to the interactive docs: api.planable.io/api/v1/docs
That's everything your developer needs to start building.
Managing your tokens
You can review and manage every token at any time from Company settings → API tokens.
- See active tokens — name, scope, workspace access, expiry, and the user who created each one
- Revoke a token — disconnect it instantly. Once revoked, the token stops working immediately and any tool using it will lose access
- Generate a new token — repeat the steps above. To "rotate" a token, generate a new one, swap it in your tool, and then revoke the old one
Each company can have up to 10 active tokens at a time. If you hit the limit, revoke one you no longer use before creating a new one. Revoked tokens are removed from the list and cannot be restored.
🔒 A note on security: API tokens are powerful; please treat them like passwords.
Never paste a token into a public document, a Slack channel, or a Git repository. Store them in a password manager, use a read-only scope whenever possible, and limit each token to specific workspaces if you don't need full company access. If you suspect a token has leaked, revoke it immediately and generate a new one.
Public API vs MCP vs Zapier — which one do I want?
Planable offers three ways to connect to other tools. They do different things:
| Integration | Best for | Who uses it |
|---|---|---|
| Public API | Custom scripts, internal tools, and automation pipelines | Your developer or technical team |
| MCP | AI assistants like Claude, ChatGPT, or Gemini | You, directly from your AI tool |
| Zapier | No-code automations between Planable and 5,000+ apps | Anyone — no developer needed |
These don't replace each other. You can have all three running at the same time if you want.