Microsoft Planner
Microsoft Planner is a task management tool that helps teams organize work, assign tasks, share files, and collaborate on projects within Microsoft 365.
Reference-quality API operations across every facet — a rich contract, published governance, transparent operations, and machine-readable commercial terms.
API Evangelist profiles Microsoft Planner the way a machine reads it — 190 machine-readable artifacts across 7 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 — Microsoft Planner scores 73.8/100 (exemplar), 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 Microsoft Planner
Each block below is one kind of artifact we hold for Microsoft Planner. 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 7
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.
Microsoft Graph Planner API (Beta)
Beta version of the Planner API in Microsoft Graph providing access to preview features including plannerRoster resources, business scenarios integration, and expanded container...
Microsoft Graph Business Scenarios Planner API (Beta)
Beta API for integrating external business processes with Microsoft Planner through business scenarios, allowing creation of scenario-controlled Planner tasks and plans.
Microsoft Planner Buckets API
Operations for managing Planner buckets
Microsoft Planner Plan Details API
Operations for managing additional plan details
Microsoft Planner Plans API
Operations for managing Planner plans
Microsoft Planner Task Details API
Operations for managing additional task details
Microsoft Planner Tasks API
Operations for managing Planner tasks
Scroll within the panel for all 7 ·
Postman Collections 1
A runnable collection turns the contract into something a developer can execute in seconds. We profile them because the fastest way to trust an API is to make a real call against it.
Ready-to-run Postman collections for exercising this provider's APIs.
Open Collections 1
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).
Microsoft Planner Microsoft Graph Planner API
OPEN COLLECTIONArazzo Workflows 8
Real integrations are rarely a single call. Arazzo describes the multi-step sequences — auth, then create, then confirm — so both a human and an agent can follow the choreography, not just the endpoints.
Multi-step API workflows described with the Arazzo specification.
Microsoft Planner Add a Bucket and Task to an Existing Plan
Confirm a plan exists, create a new bucket in it, then add a task to that bucket.
ARAZZOMicrosoft Planner Complete My First Assigned Task
List tasks assigned to the signed-in user and, if any exist, mark the first one complete.
ARAZZOMicrosoft Planner Mark a Task Complete
Read a task to capture its ETag, then patch it to 100 percent complete.
ARAZZOMicrosoft Planner Stand Up a Plan with a Bucket and First Task
Create a plan in a group, add a bucket to it, then create the first task in that bucket.
ARAZZOMicrosoft Planner Create a Task and Populate Its Details
Create a task in a plan, then read and update its task details with a description and checklist.
ARAZZOMicrosoft Planner Drill From Group to Plan to Tasks
List a group's plans, pick the first plan, and list that plan's tasks and buckets.
ARAZZOMicrosoft Planner Move a Task Into a Different Bucket
Confirm the target bucket exists, read the task ETag, then reassign the task to that bucket.
ARAZZOMicrosoft Planner Rename a Plan and Describe Its Categories
Read a plan and its details for ETags, rename the plan, then set category label descriptions.
ARAZZOScroll 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.
Microsoft Planner 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.
Microsoft Planner Finops
FINOPSFeatures 10
The notable capabilities this provider advertises, captured as structured features so they can be searched and compared instead of read one landing page at a time.
Notable capabilities this provider offers.
Scroll within the panel for all 10 ·
Semantic Vocabularies 1
JSON-LD contexts give the data shared meaning across APIs. We profile them because semantics are what let a machine reconcile 'customer' here with 'customer' somewhere else.
JSON-LD contexts and semantic vocabularies used across these APIs.
Microsoft Planner Context
JSON-LDSpectral Rules 2
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.
Microsoft Planner API Rules
SPECTRALMicrosoft Planner API Rules
SPECTRALJSON Schema 58
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.
Identity
JSON SCHEMAIdentitySet
JSON SCHEMAIdentitySet
JSON SCHEMAODataError
JSON SCHEMAODataError
JSON SCHEMAPlannerAppliedCategories
JSON SCHEMAPlannerAssignment
JSON SCHEMAPlannerAssignments
JSON SCHEMAPlannerBucketCollection
JSON SCHEMAPlannerBucketCreate
JSON SCHEMAPlannerBucket
JSON SCHEMAPlannerBucketUpdate
JSON SCHEMAPlannerCategoryDescriptions
JSON SCHEMAPlannerChecklistItem
JSON SCHEMAPlannerChecklistItems
JSON SCHEMAPlannerExternalReference
JSON SCHEMAPlannerExternalReferences
JSON SCHEMAPlannerPlanCollection
JSON SCHEMAPlannerPlanContainer
JSON SCHEMAPlannerPlanCreate
JSON SCHEMAPlannerPlanDetails
JSON SCHEMAPlannerPlanDetailsUpdate
JSON SCHEMAPlannerPlan
JSON SCHEMAPlannerPlanUpdate
JSON SCHEMAPlannerTaskCollection
JSON SCHEMAPlannerTaskCreate
JSON SCHEMAPlannerTaskDetails
JSON SCHEMAPlannerTaskDetailsUpdate
JSON SCHEMAPlannerTask
JSON SCHEMAPlannerTaskUpdate
JSON SCHEMAPlannerUserIds
JSON SCHEMAPlannerAppliedCategories
JSON SCHEMAPlannerAssignment
JSON SCHEMAPlannerAssignments
JSON SCHEMAPlannerBucket
JSON SCHEMAPlannerBucketCollection
JSON SCHEMAPlannerBucketCreate
JSON SCHEMAPlannerBucketUpdate
JSON SCHEMAPlannerCategoryDescriptions
JSON SCHEMAPlannerChecklistItem
JSON SCHEMAPlannerChecklistItems
JSON SCHEMAPlannerExternalReference
JSON SCHEMAPlannerExternalReferences
JSON SCHEMAPlannerPlan
JSON SCHEMAPlannerPlanCollection
JSON SCHEMAPlannerPlanContainer
JSON SCHEMAPlannerPlanCreate
JSON SCHEMAPlannerPlanDetails
JSON SCHEMAPlannerPlanDetailsUpdate
JSON SCHEMAPlannerPlanUpdate
JSON SCHEMAPlannerTask
JSON SCHEMAPlannerTaskCollection
JSON SCHEMAPlannerTaskCreate
JSON SCHEMAPlannerTaskDetails
JSON SCHEMAPlannerTaskDetailsUpdate
JSON SCHEMAPlannerTaskUpdate
JSON SCHEMAPlannerUserIds
JSON SCHEMAMicrosoft Planner Task
JSON SCHEMAScroll within the panel for all 58 ·
JSON Structure 30
JSON Structure captures the data shapes in a form built for tooling — a complement to JSON Schema that keeps the model machine-legible.
JSON Structure definitions describing this provider's data shapes.
Microsoft Planner Identity Set Structure
JSON STRUCTUREMicrosoft Planner Identity Structure
JSON STRUCTUREMicrosoft Planner O Data Error Structure
JSON STRUCTUREMicrosoft Planner Planner Applied Categories Structure
JSON STRUCTUREMicrosoft Planner Planner Assignment Structure
JSON STRUCTUREMicrosoft Planner Planner Assignments Structure
JSON STRUCTUREMicrosoft Planner Planner Bucket Collection Structure
JSON STRUCTUREMicrosoft Planner Planner Bucket Create Structure
JSON STRUCTUREMicrosoft Planner Planner Bucket Structure
JSON STRUCTUREMicrosoft Planner Planner Bucket Update Structure
JSON STRUCTUREMicrosoft Planner Planner Checklist Item Structure
JSON STRUCTUREMicrosoft Planner Planner Checklist Items Structure
JSON STRUCTUREMicrosoft Planner Planner External Reference Structure
JSON STRUCTUREMicrosoft Planner Planner External References Structure
JSON STRUCTUREMicrosoft Planner Planner Plan Collection Structure
JSON STRUCTUREMicrosoft Planner Planner Plan Container Structure
JSON STRUCTUREMicrosoft Planner Planner Plan Create Structure
JSON STRUCTUREMicrosoft Planner Planner Plan Details Structure
JSON STRUCTUREMicrosoft Planner Planner Plan Details Update Structure
JSON STRUCTUREMicrosoft Planner Planner Plan Structure
JSON STRUCTUREMicrosoft Planner Planner Plan Update Structure
JSON STRUCTUREMicrosoft Planner Planner Task Collection Structure
JSON STRUCTUREMicrosoft Planner Planner Task Create Structure
JSON STRUCTUREMicrosoft Planner Planner Task Details Structure
JSON STRUCTUREMicrosoft Planner Planner Task Details Update Structure
JSON STRUCTUREMicrosoft Planner Planner Task Structure
JSON STRUCTUREMicrosoft Planner Planner Task Update Structure
JSON STRUCTUREMicrosoft Planner Planner User Ids Structure
JSON STRUCTUREMicrosoft Planner Structure
JSON STRUCTUREScroll within the panel for all 30 ·
Examples 48
Real request and response payloads are what turn a spec from abstract into obvious — and they're one of the twelve things an agent needs to call an API correctly on the first try.
Example request and response payloads for these APIs.
Scroll within the panel for all 48 ·
Security Posture 3
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.
Use Cases 8
What developers actually build with this provider — captured so the catalogue answers 'what is this for', not just 'what does this expose'.
What developers build with this provider.
Scroll within the panel for all 8 ·
Integrations 8
Pre-built integrations with other platforms tell you where this provider already fits in a stack.
Pre-built integrations with other platforms and tools.
Scroll within the panel for all 8 ·
Resources
Every other property we hold for Microsoft Planner — 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 5
Portal, sign-up, and the first successful call
Documentation 3
Reference material describing how the API behaves
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 11
Pagination, idempotency, versioning, errors, and events
Scroll within the panel for all 11 ·
Build 3
SDKs, sample code, and the tooling you integrate with
Access & Security 5
Authentication, authorization, and security posture
Operate 5
Status, limits, changes, and where to get help
Commercial 2
Pricing, plans, and the legal terms of use
Company 1
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/microsoft-planner · machine-readable index on apis.io