Microsoft Teams API Documentation

This is the complete API documentation for connecting to the Microsoft Teams API using MindCloud's Universal API. If you are new to MindCloud, start with the Introduction to see how one API can sit in front of many different apps.

MindCloud is an integration company that offers one normalized API to access 3,100+ apps from a single place. It cleans up provider-specific quirks, keeps requests and responses consistent, and centralizes authentication so you do not need to manage separate flows for every app. Browse other apps.

Meet Microsoft Teams: Access Microsoft Teams collaboration data and actions through Microsoft Graph, including teams, channels, chats, messages, tabs, files folders, and installed apps. This app uses delegated Microsoft Entra OAuth2 for work or school accounts. Keep reading to get started.

Quickstart

Before you run your first Microsoft Teams request, you need three things:

1. A MindCloud account — sign in or create an account at MindCloud.
2. A MindCloud API Key — create one in API Keys. Keep it on your server.
3. At least one Microsoft Teams connection — create or choose one in Connections. Note its connectionId.

Every Microsoft Teams action uses the same URL pattern:

https://connect.mindcloud.co/v1/universal/microsoftTeams/latest/actions/{actionSlug}

You need a MindCloud API Key and a Microsoft Teams connection. Then call an action such as Get Channel:

curl --request GET \
  --url "https://connect.mindcloud.co/v1/universal/microsoftTeams/latest/actions/get-channel" \
  --header "Authorization: Bearer $MINDCLOUD_API_KEY" \
  --get \
  --data-urlencode "connectionId=$CONNECTION_ID"

Every response comes back in the same envelope, with your rows in a data array:

{
  "success": true,
  "data": [
    { "id": "1042", "name": "Ava" }
  ],
  "meta": {}
}

After your first request works, use Shape your requests to control arguments, pagination, filtering, fields, and errors.

Authentication

Authentication has two layers. Your MindCloud API Key authenticates the request to MindCloud, sent as a Bearer token in the Authorization header. The connectionId selects the connected Microsoft Teams account that should run the action. MindCloud stores and refreshes the Microsoft Teams credentials behind that connection, so you never send provider tokens with your requests.

Pass connectionId in the query string for GET and DELETE actions, and in the JSON body for POST, PUT, and PATCH actions. Keep your MindCloud API Key on your server; do not ship it in browser code, mobile apps, public repositories, or logs.

Microsoft Teams actions

All 23 published actions for this Microsoft Teams version. Each page documents the endpoint, arguments, and response controls.

• POSTCreate Channel
• POSTCreate Chat
• GETGet Channel
• GETGet Channel Files Folder
• GETGet Chat
• GETGet Team
• GETGet Team Primary Channel
• GETList All Team Channels
• GETList Channel Members
• GETList Channel Message Replies
• GETList Channel Messages
• GETList Channel Tabs
• GETList Chat Members
• GETList Chat Messages
• GETList Chats
• GETList Joined Teams
• GETList Team Channels
• GETList Team Installed Apps
• GETList Team Members
• POSTReply To Channel Message
• POSTSend Channel Message
• POSTSend Chat Message
• PUTUpdate Channel

Related apps

More Communication apps on the Universal API, behind the same REST shape. Or browse all apps.

GmailSlackDiscordTwilioCircletl;dvClickSend SMSChatwork