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 Exchange Messages API

Operations for managing email messages

Microsoft Exchange Messages API is one of 20 APIs that Microsoft Exchange publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Message. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, authentication docs, a getting-started guide, a changelog, and an API reference.

This API exposes 17 operations across 13 paths, and defines 9 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.

17 operations 13 paths 9 schemas 1 DELETE3 GET1 PATCH12 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 Exchange Messages API declares 1 security scheme for authenticating requests. It supports OAuth 2.0 (oauth2) using the authorizationCode flow, exposing 4 scopes. By default, every request must be authenticated.

  • oauth2 — OAuth 2.0 authorization with Microsoft identity platform

Paths & Operations 17

Across 13 paths, the API surfaces 17 operations — 1 DELETE, 3 GET, 1 PATCH, 12 POST. Each is listed below with its method, path, parameters, and response codes.

Messages 17

Operations for managing email messages

GET
/me/messages
Microsoft Exchange List messages
listMessages 6 params → 200401403
POST
/me/messages
Microsoft Exchange Create draft message
createDraftMessage body → 201400401
GET
/me/messages/{message-id}
Microsoft Exchange Get message
getMessage 2 params → 200401404
PATCH
/me/messages/{message-id}
Microsoft Exchange Update message
updateMessage 1 param body → 200400401404
DELETE
/me/messages/{message-id}
Microsoft Exchange Delete message
deleteMessage 1 param → 204401404
POST
/me/messages/{message-id}/send
Microsoft Exchange Send draft message
sendDraftMessage 1 param → 202401404
POST
/me/messages/{message-id}/reply
Microsoft Exchange Reply to message
replyToMessage 1 param body → 202401404
POST
/me/messages/{message-id}/replyAll
Microsoft Exchange Reply all to message
replyAllToMessage 1 param body → 202401404
POST
/me/messages/{message-id}/forward
Microsoft Exchange Forward message
forwardMessage 1 param body → 202401404
POST
/me/messages/{message-id}/copy
Microsoft Exchange Copy message
copyMessage 1 param body → 201401404
POST
/me/messages/{message-id}/move
Microsoft Exchange Move message
moveMessage 1 param body → 201401404
POST
/me/messages/{message-id}/createReply
Microsoft Exchange Create reply draft
createReplyDraft 1 param body → 201401404
POST
/me/messages/{message-id}/createReplyAll
Microsoft Exchange Create reply-all draft
createReplyAllDraft 1 param body → 201401404
POST
/me/messages/{message-id}/createForward
Microsoft Exchange Create forward draft
createForwardDraft 1 param body → 201401404
POST
/me/sendMail
Microsoft Exchange Send mail
sendMail body → 202400401
GET
/me/mailFolders/{mailFolder-id}/messages
Microsoft Exchange List messages in mail folder
listMailFolderMessages 6 params → 200401404
POST
/me/mailFolders/{mailFolder-id}/messages
Microsoft Exchange Create message in folder
createMessageInFolder 1 param body → 201400401

Schemas 9

The contract defines 9 schemas that model the data the API accepts and returns. The most detailed are Message (31 properties), FollowupFlag (4 properties), MessageCollectionResponse (3 properties), EmailAddress (2 properties). Each schema is shown below with its type and property counts.

FollowupFlag
object
Follow-up flag on a message
4 properties
MessageCollectionResponse
object
Collection of messages
3 properties
EmailAddress
object
Represents the name and email address of a contact or message recipient
2 properties
DateTimeTimeZone
object
Describes the date, time, and time zone of a point in time
2 properties
InternetMessageHeader
object
A key-value pair representing an Internet message header
2 properties
Recipient
object
Represents an email recipient
1 property
ODataError
object
OData error response
1 property
Message
object
A message in a mailFolder
31 properties
ItemBody
object
Represents the body of a message or event
2 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

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

Other APIs Microsoft Exchange publishes across the network.

Exchange Web Services (EWS)
Exchange Online PowerShell API
Exchange Autodiscover API
Microsoft Exchange Accepted Domains API
Microsoft Exchange Attachments API
Microsoft Exchange Calendars API
Microsoft Exchange Contact Folders API
Microsoft Exchange Contacts API
Microsoft Exchange Distribution Groups API
Microsoft Exchange Events API
Microsoft Exchange Mail Folders API
Microsoft Exchange Mailbox Discovery API
Where this information came from

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