Planable
Planable is a social media collaboration platform trusted by agencies, freelancers, and marketing teams to plan, create, collaborate, approve, and publish content across multiple social media channels. It provides a REST API for managing workspaces, pages, posts, feedback, approval workflows, and publishing to Facebook, Instagram, LinkedIn, X (Twitter), YouTube, TikTok, Pinterest, Google Business Profile, and Threads.
Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.
API Evangelist profiles Planable the way a machine reads it — 166 machine-readable artifacts across 8 APIs, 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 51.1/100 (developing), with a separate agent-readiness read of 48/100 (agent ready). 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.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
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 8
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 — 2 operation(s) for campaigns.
Planable Labels API
The Labels API from Planable — 1 operation(s) for labels.
Planable Media API
The Media API from Planable — 2 operation(s) for media.
Planable Pages API
The Pages API from Planable — 4 operation(s) for pages.
Planable Posts API
The Posts API from Planable — 8 operation(s) for posts.
Planable Stories API
The Stories API from Planable — 1 operation(s) for stories.
Planable System API
The System API from Planable — 1 operation(s) for system.
Planable Workspaces API
The Workspaces API from Planable — 2 operation(s) for workspaces.
Scroll within the panel for all 8 ·
Pricing 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 six things the Kin Score reads for commercial clarity.
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.
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.
Documentation 1
Reference material describing how the API behaves
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 2
Authentication, authorization, and security posture
Operate 3
Status, limits, changes, and where to get help
Commercial 3
Pricing, plans, and the legal terms of use
Company 3
The organization behind the API
Other 1
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