Planable
Planable is a collaboration-first social media management platform used by agencies, multi-location brands, multi-brand companies and in-house marketing teams to create, plan, collaborate on, approve, schedule, publish and analyze content across Facebook, Instagram, X (Twitter), LinkedIn, TikTok, YouTube, Pinterest, Threads and Google Business Profile. It exposes three programmable surfaces: a REST Public API v1 at https://api.planable.io/api/v1 with 51 operations over workspaces, pages, posts, comments, campaigns, labels, media, members, stories, competitor analytics and social listening; a remote OAuth-protected MCP server at https://mcp.planable.io/mcp for Claude, ChatGPT and Gemini; and twelve MIT-licensed Agent Skills published as a Claude Code plugin. Agent- and API-created content always lands as a draft and passes through Planable's normal approval workflow.
Solid contracts, transparent operations, and an easy start — typically complete on four or five facets with one clear soft spot.
API Evangelist profiles Planable the way a machine reads it — 181 machine-readable artifacts across 1 API, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Planable scores 59.2/100 (strong), with a separate agent-readiness read of 52/100 (agent native). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance. Every facet and dimension name is a link: it opens that measurement's page on APIs.io, where the rating runs across the whole catalog — the exact checks that feed it, how every profiled provider distributes on it, and who is at the top of it.
Kin Score
How this is scored →scored 2026-09-08 · rubric v0.20.0
Put this on your own site. The badge is drawn live from Planable's current Kin Score — paste it once and it updates itself every time the score is recomputed. It follows your visitor's light or dark setting, and it links back here so anyone who sees it can read the full breakdown.
<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/planable/"
title="Planable on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/planable.svg"
alt="Planable Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/planable/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/planable/"
title="Planable on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/planable/card.svg"
alt="Planable Kin Score — API readiness rating by API Evangelist" width="340" height="120" loading="lazy">
</a>More shapes, themes and sizes → · Score as JSON · How badges work
How we profile Planable
Each block below is one kind of artifact we hold for Planable. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 12
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Planable Campaigns API
The Campaigns API from Planable — 5 operation(s). Create, read, update and delete campaigns — named groupings of posts inside a workspace.
Planable Competitors API
The Competitors API from Planable — 6 operation(s). Track up to five competitor social pages per page and pull comparison tables, follower/engagement trends and competitor top p...
Planable Labels API
The Labels API from Planable — 2 operation(s). List and create the color-coded labels used to organize posts by topic, format or event within a workspace.
Planable Media API
The Media API from Planable — 3 operation(s). List the workspace media library, upload assets from a public URL (up to 100MB per file) and read an asset’s type, dimensions and p...
Planable Members API
The Members API from Planable — 1 operation(s). List workspace members with their roles and approval-level assignments.
Planable Pages API
The Pages API from Planable — 4 operation(s). List the social channels connected to a workspace, pull per-page analytics, and trigger and poll a metrics sync from the source pla...
Planable Posts API
The Posts API from Planable — 18 operation(s). The core content surface — list, create, read, update and delete posts, create synced cross-platform group posts, manage comments ...
Planable Social Listening API
The Social Listening API from Planable — 7 operation(s). Track brand and topic keywords for a workspace, then read matched mentions, daily metrics, aggregated summaries and sync...
Planable Stories API
The Stories API from Planable — 1 operation(s). Create single-frame or multi-frame Instagram and Facebook stories.
Planable System API
The System API from Planable — 1 operation(s). Health check for the Planable Public API.
Planable Workspaces API
The Workspaces API from Planable — 3 operation(s). List, create and delete the workspaces that scope every other resource in the API.
Planable MCP Server
Planable’s official remote Model Context Protocol server at https://mcp.planable.io/mcp. An OAuth 2.0 protected resource (authorization code + PKCE, dynamic client registration,...
Scroll within the panel for all 12 ·
Open Collections 9
Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
API Collection
OPEN COLLECTIONPlanable Public Campaigns API
OPEN COLLECTIONPlanable Public Campaigns Labels API
OPEN COLLECTIONPlanable Public Campaigns Media API
OPEN COLLECTIONPlanable Public Campaigns Pages API
OPEN COLLECTIONPlanable Public Campaigns Posts API
OPEN COLLECTIONPlanable Public Campaigns Stories API
OPEN COLLECTIONPlanable Public Campaigns System API
OPEN COLLECTIONPlanable Public Campaigns Workspaces API
OPEN COLLECTIONScroll within the panel for all 9 ·
MCP Servers 1
Model Context Protocol servers expose these APIs directly to AI agents. We profile them because agent-native access is the fastest-growing way this provider's capabilities actually get used.
Model Context Protocol servers that expose these APIs to AI agents.
Planable MCP
Planable's official remote MCP server. It gives any MCP-capable AI client (Claude, ChatGPT, Gemini) read and write access to the signed-in user's Planable account — companies, w...
MCP SERVERPricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the things the Kin Score reads for access clarity — renamed from commercial clarity in rubric 0.12, because a free statutory interface has access terms and no commercial ones.
Published pricing tiers and plan structures.
Rate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Planable Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.
Cost, billing, and metering signals for API financial operations.
Planable Finops
FINOPSSpectral Rules 1
Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.
Planable API Rules
SPECTRALJSON Schema 151
Standalone JSON Schema definitions describe the data models behind the API. We profile them so the shapes are validatable on their own — useful long after a single request is forgotten.
Standalone JSON Schema definitions for this provider's data models.
Delete_Campaigns_{Id} Response 401
JSON SCHEMADelete_Campaigns_{Id} Response 429
JSON SCHEMADelete_Campaigns_{Id} Response 500
JSON SCHEMADelete_Posts_{Id} Response 401
JSON SCHEMADelete_Posts_{Id} Response 429
JSON SCHEMADelete_Posts_{Id} Response 500
JSON SCHEMADelete_Workspaces_{Id} Response 401
JSON SCHEMADelete_Workspaces_{Id} Response 429
JSON SCHEMADelete_Workspaces_{Id} Response 500
JSON SCHEMAGet_Campaigns Response 200
JSON SCHEMAGet_Campaigns Response 401
JSON SCHEMAGet_Campaigns Response 403
JSON SCHEMAGet_Campaigns Response 429
JSON SCHEMAGet_Campaigns Response 500
JSON SCHEMAGet_Campaigns_{Id} Response 200
JSON SCHEMAGet_Campaigns_{Id} Response 401
JSON SCHEMAGet_Campaigns_{Id} Response 403
JSON SCHEMAGet_Campaigns_{Id} Response 429
JSON SCHEMAGet_Campaigns_{Id} Response 500
JSON SCHEMAGet_Labels Response 200
JSON SCHEMAGet_Labels Response 401
JSON SCHEMAGet_Labels Response 403
JSON SCHEMAGet_Labels Response 429
JSON SCHEMAGet_Labels Response 500
JSON SCHEMAGet_Media Response 200
JSON SCHEMAGet_Media Response 401
JSON SCHEMAGet_Media Response 403
JSON SCHEMAGet_Media Response 429
JSON SCHEMAGet_Media Response 500
JSON SCHEMAGet_Media_{Id} Response 200
JSON SCHEMAGet_Media_{Id} Response 401
JSON SCHEMAGet_Media_{Id} Response 403
JSON SCHEMAGet_Media_{Id} Response 429
JSON SCHEMAGet_Media_{Id} Response 500
JSON SCHEMAGet_Pages Response 200
JSON SCHEMAGet_Pages Response 401
JSON SCHEMAGet_Pages Response 403
JSON SCHEMAGet_Pages Response 429
JSON SCHEMAGet_Pages Response 500
JSON SCHEMAGet_Pages_{Id}_Metrics Response 200
JSON SCHEMAGet_Pages_{Id}_Metrics Response 401
JSON SCHEMAGet_Pages_{Id}_Metrics Response 429
JSON SCHEMAGet_Pages_{Id}_Metrics Response 500
JSON SCHEMAGet_Pages_{Id}_Sync Status Response 200
JSON SCHEMAGet_Pages_{Id}_Sync Status Response 401
JSON SCHEMAGet_Pages_{Id}_Sync Status Response 429
JSON SCHEMAGet_Pages_{Id}_Sync Status Response 500
JSON SCHEMAGet_Ping Response 200
JSON SCHEMAGet_Ping Response 401
JSON SCHEMAGet_Ping Response 403
JSON SCHEMAGet_Ping Response 429
JSON SCHEMAGet_Ping Response 500
JSON SCHEMAGet_Posts Response 200
JSON SCHEMAGet_Posts Response 401
JSON SCHEMAGet_Posts Response 403
JSON SCHEMAGet_Posts Response 429
JSON SCHEMAGet_Posts Response 500
JSON SCHEMAGet_Posts_Count Response 200
JSON SCHEMAGet_Posts_Count Response 401
JSON SCHEMAGet_Posts_Count Response 403
JSON SCHEMAGet_Posts_Count Response 429
JSON SCHEMAGet_Posts_Count Response 500
JSON SCHEMAGet_Posts_{Id} Response 200
JSON SCHEMAGet_Posts_{Id} Response 401
JSON SCHEMAGet_Posts_{Id} Response 403
JSON SCHEMAGet_Posts_{Id} Response 429
JSON SCHEMAGet_Posts_{Id} Response 500
JSON SCHEMAGet_Posts_{Id}_Comments Response 200
JSON SCHEMAGet_Posts_{Id}_Comments Response 401
JSON SCHEMAGet_Posts_{Id}_Comments Response 403
JSON SCHEMAGet_Posts_{Id}_Comments Response 429
JSON SCHEMAGet_Posts_{Id}_Comments Response 500
JSON SCHEMAGet_Posts_{Id}_Metrics Response 200
JSON SCHEMAGet_Posts_{Id}_Metrics Response 401
JSON SCHEMAGet_Posts_{Id}_Metrics Response 403
JSON SCHEMAGet_Posts_{Id}_Metrics Response 429
JSON SCHEMAGet_Posts_{Id}_Metrics Response 500
JSON SCHEMAGet_Posts_{Id}_Sync Status Response 200
JSON SCHEMAGet_Posts_{Id}_Sync Status Response 401
JSON SCHEMAGet_Posts_{Id}_Sync Status Response 429
JSON SCHEMAGet_Posts_{Id}_Sync Status Response 500
JSON SCHEMAGet_Workspaces Response 200
JSON SCHEMAGet_Workspaces Response 401
JSON SCHEMAGet_Workspaces Response 403
JSON SCHEMAGet_Workspaces Response 429
JSON SCHEMAGet_Workspaces Response 500
JSON SCHEMAPatch_Campaigns_{Id} Request
JSON SCHEMAPatch_Campaigns_{Id} Response 200
JSON SCHEMAPatch_Campaigns_{Id} Response 401
JSON SCHEMAPatch_Campaigns_{Id} Response 429
JSON SCHEMAPatch_Campaigns_{Id} Response 500
JSON SCHEMAPatch_Posts_Reorder Request
JSON SCHEMAPatch_Posts_Reorder Response 200
JSON SCHEMAPatch_Posts_Reorder Response 401
JSON SCHEMAPatch_Posts_Reorder Response 403
JSON SCHEMAPatch_Posts_Reorder Response 429
JSON SCHEMAPatch_Posts_Reorder Response 500
JSON SCHEMAPatch_Posts_{Id} Request
JSON SCHEMAPatch_Posts_{Id} Response 200
JSON SCHEMAPatch_Posts_{Id} Response 401
JSON SCHEMAPatch_Posts_{Id} Response 403
JSON SCHEMAPatch_Posts_{Id} Response 429
JSON SCHEMAPatch_Posts_{Id} Response 500
JSON SCHEMAPost_Campaigns Request
JSON SCHEMAPost_Campaigns Response 201
JSON SCHEMAPost_Campaigns Response 401
JSON SCHEMAPost_Campaigns Response 429
JSON SCHEMAPost_Campaigns Response 500
JSON SCHEMAPost_Labels Request
JSON SCHEMAPost_Labels Response 201
JSON SCHEMAPost_Labels Response 401
JSON SCHEMAPost_Labels Response 403
JSON SCHEMAPost_Labels Response 429
JSON SCHEMAPost_Labels Response 500
JSON SCHEMAPost_Media Request
JSON SCHEMAPost_Media Response 202
JSON SCHEMAPost_Media Response 401
JSON SCHEMAPost_Media Response 403
JSON SCHEMAPost_Media Response 429
JSON SCHEMAPost_Media Response 500
JSON SCHEMAPost_Pages_{Id}_Sync Response 200
JSON SCHEMAPost_Pages_{Id}_Sync Response 401
JSON SCHEMAPost_Pages_{Id}_Sync Response 429
JSON SCHEMAPost_Pages_{Id}_Sync Response 500
JSON SCHEMAPost_Posts Request
JSON SCHEMAPost_Posts Response 201
JSON SCHEMAPost_Posts Response 401
JSON SCHEMAPost_Posts Response 403
JSON SCHEMAPost_Posts Response 429
JSON SCHEMAPost_Posts Response 500
JSON SCHEMAPost_Posts_{Id}_Comments Request
JSON SCHEMAPost_Posts_{Id}_Comments Response 201
JSON SCHEMAPost_Posts_{Id}_Comments Response 401
JSON SCHEMAPost_Posts_{Id}_Comments Response 403
JSON SCHEMAPost_Posts_{Id}_Comments Response 429
JSON SCHEMAPost_Posts_{Id}_Comments Response 500
JSON SCHEMAPost_Posts_{Id}_Sync Response 200
JSON SCHEMAPost_Posts_{Id}_Sync Response 401
JSON SCHEMAPost_Posts_{Id}_Sync Response 429
JSON SCHEMAPost_Posts_{Id}_Sync Response 500
JSON SCHEMAPost_Stories Request
JSON SCHEMAPost_Stories Response 201
JSON SCHEMAPost_Stories Response 401
JSON SCHEMAPost_Stories Response 403
JSON SCHEMAPost_Stories Response 429
JSON SCHEMAPost_Stories Response 500
JSON SCHEMAPost_Workspaces Request
JSON SCHEMAPost_Workspaces Response 201
JSON SCHEMAPost_Workspaces Response 401
JSON SCHEMAPost_Workspaces Response 429
JSON SCHEMAPost_Workspaces Response 500
JSON SCHEMAScroll within the panel for all 151 ·
Security Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Scopes 1
OAuth scopes are the vocabulary of least-privilege access. Profiling them shows exactly what an integration — or an agent acting on a user's behalf — is allowed to do.
OAuth scopes governing access to this provider's APIs.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for Planable — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 4
Portal, sign-up, and the first successful call
Documentation 4
Reference material describing how the API behaves
Agent Surfaces 5
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 9
Pagination, idempotency, versioning, errors, and events
Scroll within the panel for all 9 ·
Build 3
SDKs, sample code, and the tooling you integrate with
Access & Security 3
Authentication, authorization, and security posture
Operate 4
Status, limits, changes, and where to get help
Commercial 6
Pricing, plans, and the legal terms of use
Company 3
The organization behind the API
Other 3
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/planable · machine-readable index on apis.io
This is an independent, third-party profile of Planable, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.
The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.
Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.
info@apievangelist.com
·
Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and
you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.