Microsoft Teams
Microsoft Teams is a collaboration platform that combines workplace chat, meetings, file storage, and application integration. It provides APIs for building custom integrations, managing teams and channels, sending messages, scheduling meetings, and initiating calls through Microsoft Graph.
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 Microsoft Teams the way a machine reads it — 114 machine-readable artifacts across 11 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 Teams scores 53.2/100 (developing), with a separate agent-readiness read of 35/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. 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 Microsoft Teams'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/microsoft-teams/"
title="Microsoft Teams on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/microsoft-teams.svg"
alt="Microsoft Teams Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/microsoft-teams/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/microsoft-teams/"
title="Microsoft Teams on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/microsoft-teams/card.svg"
alt="Microsoft Teams 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 Microsoft Teams
Each block below is one kind of artifact we hold for Microsoft Teams. 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 11
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 Teams Bot Framework API
API for building conversational bots that interact with users in Microsoft Teams through the Bot Framework.
Microsoft Teams Webhook and Connector API
APIs for creating incoming webhooks and Office 365 connectors to post messages and notifications to Teams channels.
Microsoft Teams Real-Time Communication APIs
APIs for building calling and meeting experiences in Teams including VoIP calls, group calls, IVR flows, and online meetings.
Microsoft Teams Apps API
Operations for managing app installations in teams.
Microsoft Teams Calls API
Operations for initiating and managing calls.
Microsoft Teams Channels API
Operations for managing channels within teams.
Microsoft Teams Members API
Operations for managing team and channel members.
Microsoft Teams Messages API
Operations for sending and receiving chat messages.
Microsoft Teams Online Meetings API
Operations for creating and managing online meetings.
Microsoft Teams Tabs API
Operations for managing tabs in channels.
Microsoft Teams Teams API
Operations for managing teams.
Scroll within the panel for all 11 ·
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.
Microsoft Graph Teams API
POSTMANOpen 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 COLLECTIONMicrosoft Graph Teams Apps API
OPEN COLLECTIONMicrosoft Graph Teams Apps Calls API
OPEN COLLECTIONMicrosoft Graph Teams Apps Channels API
OPEN COLLECTIONMicrosoft Graph Teams Apps Members API
OPEN COLLECTIONMicrosoft Graph Teams Apps Messages API
OPEN COLLECTIONMicrosoft Graph Teams Apps Online Meetings API
OPEN COLLECTIONMicrosoft Graph Teams Apps Tabs API
OPEN COLLECTIONMicrosoft Graph Apps Teams API
OPEN COLLECTIONScroll within the panel for all 9 ·
Arazzo Workflows 14
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 Teams Add Member and Welcome
Add a member to a team and post a welcome message to a chosen channel.
ARAZZOMicrosoft Teams Archive Team
Confirm a team is active and then archive it, making it read-only.
ARAZZOMicrosoft Teams Audit Team Channels
Resolve a team and enumerate its channels for an inventory snapshot.
ARAZZOMicrosoft Teams Broadcast to Joined Team Channel
Pick one of the current user's joined teams, find a channel, and post to it.
ARAZZOMicrosoft Teams Create Team
Create a new Microsoft Teams team and capture the provisioning operation location.
ARAZZOMicrosoft Teams Discover Channel Tabs
List a team's channels and enumerate the tabs in a chosen channel.
ARAZZOMicrosoft Teams Inventory Team Collaboration
Snapshot a team's members, channels, and installed apps in one pass.
ARAZZOMicrosoft Teams Offboard Team Member
Find a member by user id in a team and remove their membership.
ARAZZOMicrosoft Teams Post Channel Announcement
Find a channel by name in a team and post an announcement message to it.
ARAZZOMicrosoft Teams Promote Team Member
List a team's members and promote an existing membership to owner.
ARAZZOMicrosoft Teams Provision Channel
Confirm a team, create a channel in it, and post an opening message.
ARAZZOMicrosoft Teams Review Channel Conversation
List a team's channels and read the recent messages in a chosen channel.
ARAZZOScroll within the panel for all 14 ·
GraphQL 1
Where a provider ships GraphQL, the schema is the contract. We profile it alongside the REST surface so the whole interface is legible in one place.
GraphQL schemas published by this provider.
Microsoft Teams GraphQL Schema
This GraphQL schema provides a conceptual representation of the Microsoft Teams API surface exposed through Microsoft Graph. It maps the core Teams resources — teams, channels, ...
GRAPHQLPricing 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.
Microsoft Teams 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 Teams Finops
FINOPSFeatures 11
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 11 ·
Event Specifications 1
Not every API is request/response. AsyncAPI describes the event-driven and streaming side — the webhooks and channels — so the asynchronous half of the interface is documented the same way the synchronous half is.
AsyncAPI definitions for this provider's event-driven and streaming APIs.
Microsoft Teams Event Surface
AsyncAPI 2.6 description of the asynchronous event surface for Microsoft Teams. Two distinct delivery channels are modeled: 1. Microsoft Graph change notifications - HTTPS webho...
ASYNCAPISemantic 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.
Spectral Rules 3
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 Teams API Rules
SPECTRALMicrosoft Teams API Rules
SPECTRALMicrosoft Teams API Rules
SPECTRALJSON Schema 21
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.
AppInstallationCollection
JSON SCHEMACall
JSON SCHEMAChannel
JSON SCHEMAChannelCollection
JSON SCHEMAChatMessage
JSON SCHEMAChatMessageCollection
JSON SCHEMAConversationMember
JSON SCHEMAErrorResponse
JSON SCHEMAMemberCollection
JSON SCHEMAOnlineMeeting
JSON SCHEMATabCollection
JSON SCHEMATeam
JSON SCHEMATeamCollection
JSON SCHEMATeamsAppInstallation
JSON SCHEMATeamsTab
JSON SCHEMACall
JSON SCHEMAChannel
JSON SCHEMAChatMessage
JSON SCHEMAConversationMember
JSON SCHEMAOnlineMeeting
JSON SCHEMATeam
JSON SCHEMAScroll within the panel for all 21 ·
JSON Structure 7
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 Teams Structure
JSON STRUCTURETeams Graph Api Call Structure
JSON STRUCTURETeams Graph Api Channel Structure
JSON STRUCTURETeams Graph Api Chat Message Structure
JSON STRUCTURETeams Graph Api Conversation Member Structure
JSON STRUCTURETeams Graph Api Online Meeting Structure
JSON STRUCTURETeams Graph Api Team Structure
JSON STRUCTUREScroll within the panel for all 7 ·
Examples 20
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.
Teams Graph Api Call Example
EXAMPLETeams Graph Api Team Example
EXAMPLEScroll within the panel for all 20 ·
Security Posture 4
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.
Microsoft Teams Trust Center
SOC 1, SOC 2, SOC 3, ISO 27001, ISO 27017, ISO 27018, ISO 27701, FedRAMP, HIPAA / HITECH, PCI DSS, CSA STAR, GDPR
SECURITYScopes 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 5
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.
Team Provisioning
Automate creation and configuration of teams for projects.
Messaging Automation
Send automated notifications and updates to channels.
Meeting Scheduling
Programmatically create and manage online meetings.
Customer Service Bots
Build conversational bots for customer support in Teams.
Workforce Management
Manage shifts and schedules for frontline workers.
Resources
Every other property we hold for Microsoft Teams — 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 3
Portal, sign-up, and the first successful call
Agent Surfaces 4
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 21
Pagination, idempotency, versioning, errors, and events
Scroll within the panel for all 21 ·
Build 5
SDKs, sample code, and the tooling you integrate with
Access & Security 5
Authentication, authorization, and security posture
Operate 3
Status, limits, changes, and where to get help
Commercial 2
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/microsoft-teams · machine-readable index on apis.io
This is an independent, third-party profile of Microsoft Teams, 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.