How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Microsoft Teams Messages API

Operations for sending and receiving chat messages.

Microsoft Teams Messages API is one of 11 APIs that Microsoft Teams publishes on the APIs.io network, described by a machine-readable OpenAPI specification and an AsyncAPI event-driven specification.

This API exposes 7 JSON Schema definitions.

Tagged areas include Message. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an AsyncAPI specification, authentication docs, rate-limit docs, a JSON-LD context, and 7 JSON Schemas.

This API exposes 2 operations across 1 path, and defines 2 schemas. It is described by OpenAPI 3.2.0, at version 1.0.0.

Requests are made against a single base URL, https://graph.microsoft.com/v1.0.

2 operations 1 paths 2 schemas 1 GET1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0.0
Base URL
https://graph.microsoft.com/v1.0
Authentication
OAuth 2.0
Resource Areas
1

Authentication & Security 1

Microsoft Teams Messages API declares 1 security scheme for authenticating requests. It supports OAuth 2.0 (oauth2) using the authorizationCode flow, exposing 10 scopes. By default, every request must be authenticated.

  • oauth2 — OAuth 2.0 authorization using Microsoft Identity Platform

Paths & Operations 2

Across 1 path, the API surfaces 2 operations — 1 GET, 1 POST. Each is listed below with its method, path, parameters, and response codes.

Messages 2

Operations for sending and receiving chat messages.

GET
/teams/{team-id}/channels/{channel-id}/messages
Microsoft Teams List Channel Messages
listChannelMessages 3 params → 200401404
POST
/teams/{team-id}/channels/{channel-id}/messages
Microsoft Teams Send Channel Message
sendChannelMessage 2 params body → 201400401

Schemas 2

The contract defines 2 schemas that model the data the API accepts and returns. The most detailed are ChatMessage (8 properties), ChatMessageCollection (1 property). Each schema is shown below with its type and property counts.

ChatMessageCollection
object
Collection of chat messages.
1 property
ChatMessage
object
Represents a message in a channel or chat.
8 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

microsoft-teams-messages-api-openapi.yml Raw ↑

Other APIs Microsoft Teams publishes across the network.

Microsoft Teams Bot Framework API
Microsoft Teams Webhook and Connector API
Microsoft Teams Real-Time Communication APIs
Microsoft Teams Apps API
Microsoft Teams Calls API
Microsoft Teams Channels API
Microsoft Teams Members API
Microsoft Teams Online Meetings API
Microsoft Teams Tabs API
Microsoft Teams Teams API
Where this information came from

This is an independent, third-party profile of Microsoft Teams Messages API, 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.