Microsoft Exchange
A comprehensive API collection for Microsoft Exchange Server and Exchange Online, providing programmatic access to email, calendars, contacts, and other mailbox resources through Microsoft Graph, EWS, PowerShell, Autodiscover, and the Exchange Online Admin API.
Reference-quality API operations across every facet — a rich contract, published governance, transparent operations, and machine-readable commercial terms.
API Evangelist profiles Microsoft Exchange the way a machine reads it — 113 machine-readable artifacts across 20 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 Exchange scores 76.6/100 (exemplar), with a separate agent-readiness read of 74/100 (agent native). 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 Exchange
Each block below is one kind of artifact we hold for Microsoft Exchange. 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 20
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.
Exchange Web Services (EWS)
Legacy SOAP-based API for Exchange Server providing comprehensive access to mailbox data and operations. Planned for deprecation in Exchange Online in October 2026, with Microso...
Exchange Online PowerShell API
PowerShell module for managing Exchange Online through REST-based cmdlets. Provides the complete Exchange management surface for administrative tasks including mailbox managemen...
Exchange Autodiscover API
Service that enables client applications to automatically configure themselves for Exchange connectivity using minimal user input. Supports SOAP and POX protocols for discoverin...
Microsoft Exchange Accepted Domains API
View accepted domains and their configurations
Microsoft Exchange Attachments API
Operations for managing message attachments
Microsoft Exchange Calendars API
Operations for managing calendars
Microsoft Exchange Contact Folders API
Operations for managing contact folders
Microsoft Exchange Contacts API
Operations for managing personal contacts
Microsoft Exchange Distribution Groups API
Retrieve distribution group and dynamic distribution group membership
Microsoft Exchange Events API
Operations for managing calendar events
Microsoft Exchange Mail Folders API
Operations for managing mail folders
Microsoft Exchange Mailbox Discovery API
Operations for discovering mailbox structure and content
Microsoft Exchange Mailbox Export API
Operations for exporting content from mailboxes
Microsoft Exchange Mailbox Folder Permissions API
View and manage mailbox folder permissions
Microsoft Exchange Mailbox Import API
Operations for importing content into mailboxes
Microsoft Exchange Mailboxes API
View and update mailbox properties and delegation
Microsoft Exchange Messages API
Operations for managing email messages
Microsoft Exchange Organization Configuration API
Retrieve organization-level Exchange configuration
Microsoft Exchange People API
Operations for retrieving relevant people
Microsoft Exchange Scheduling API
Operations for scheduling and free/busy information
Scroll within the panel for all 20 ·
Postman Collections 6
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 6
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 Exchange Exchange Online Admin API
OPEN COLLECTIONMicrosoft Exchange Microsoft Graph Calendar API
OPEN COLLECTIONMicrosoft Exchange Microsoft Graph Contacts API
OPEN COLLECTIONMicrosoft Exchange Microsoft Graph Mailbox Import Export API
OPEN COLLECTIONMicrosoft Exchange Microsoft Graph Mail API
OPEN COLLECTIONMicrosoft Exchange Microsoft Graph People API
OPEN COLLECTIONArazzo Workflows 17
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 Exchange Audit Message Attachments
Find a message that has attachments, read it, and list its attachments.
ARAZZOMicrosoft Exchange Audit Organization and Domains
Read Exchange organization configuration, then list accepted domains.
ARAZZOMicrosoft Exchange Compose, Attach, and Send Mail
Create a draft message, add a file attachment to it, then send the draft.
ARAZZOMicrosoft Exchange Discover Mailbox Content
Discover a user's mailbox, drill into its folders, and list folder items.
ARAZZOMicrosoft Exchange Find Times and Book a Meeting
Suggest meeting times for attendees, then book the top suggestion.
ARAZZOMicrosoft Exchange Grant a Mailbox Folder Permission
Read current folder permissions, then add a permission for a user.
ARAZZOMicrosoft Exchange Inspect and Delegate a Mailbox
Read a mailbox's properties, then grant Send on Behalf delegation.
ARAZZOMicrosoft Exchange Migrate a Mailbox Item
Pick a source item, export its full MIME content, and import it elsewhere.
ARAZZOMicrosoft Exchange Organize a Contacts Folder
Create a contact folder, add a contact to it, and read the contact back.
ARAZZOMicrosoft Exchange Organize a Folder and File a Message
Create a mail folder, confirm it, and create a message inside it.
ARAZZOMicrosoft Exchange Prepare and Send a Forward
Create a forward draft, edit its body, and send it to new recipients.
ARAZZOMicrosoft Exchange Provision a Calendar and Add an Event
Create a new calendar, add an event to it, and read the event back.
ARAZZOMicrosoft Exchange Reply to Latest Message from a Sender
Find the newest message from a given sender, read it, and send a reply.
ARAZZOMicrosoft Exchange Review and Respond to an Invite
List upcoming events, read the next one, and accept the invitation.
ARAZZOMicrosoft Exchange Schedule an Event with an Attachment
Create a calendar event, confirm it, then attach a file to it.
ARAZZOMicrosoft Exchange Triage and Move a Message
Find the newest unread inbox message, read it, mark it read, and file it.
ARAZZOMicrosoft Exchange Upsert a Contact
Find a contact by email and update it if it exists, otherwise create it.
ARAZZOScroll within the panel for all 17 ·
MCP Servers 1
Model Context Protocol servers expose these APIs directly to AI agents. We profile them because agent-native access is the fastest-growing way this provider's capabilities actually get used.
Model Context Protocol servers that expose these APIs to AI agents.
microsoft-exchange-mcp.yml
MCP SERVERPricing 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 Exchange 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.
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 Exchange Context
JSON-LDSpectral Rules 1
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 Exchange API Rules
SPECTRALJSON Schema 52
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.
AdminApiResponse
JSON SCHEMAAttachment
JSON SCHEMAAttachmentCollectionResponse
JSON SCHEMAAttendee
JSON SCHEMAAttendeeBase
JSON SCHEMAMicrosoft Exchange Calendar
JSON SCHEMACalendarCollectionResponse
JSON SCHEMAMicrosoft Exchange Contact
JSON SCHEMAContactCollectionResponse
JSON SCHEMAContactDeltaResponse
JSON SCHEMAContactFolder
JSON SCHEMAContactFolderCollectionResponse
JSON SCHEMADateTimeTimeZone
JSON SCHEMAEmailAddress
JSON SCHEMAMicrosoft Exchange Calendar Event
JSON SCHEMAEventCollectionResponse
JSON SCHEMAFollowupFlag
JSON SCHEMAInternetMessageHeader
JSON SCHEMAItemBody
JSON SCHEMALocation
JSON SCHEMALocationConstraint
JSON SCHEMALocationConstraintItem
JSON SCHEMAMicrosoft Exchange Mail Folder
JSON SCHEMAMailbox
JSON SCHEMAMailboxFolder
JSON SCHEMAMailboxItem
JSON SCHEMAMailFolder
JSON SCHEMAMailFolderCollectionResponse
JSON SCHEMAMeetingTimeSuggestion
JSON SCHEMAMeetingTimeSuggestionsResult
JSON SCHEMAMicrosoft Exchange Message
JSON SCHEMAMessageCollectionResponse
JSON SCHEMAODataError
JSON SCHEMAOnlineMeetingInfo
JSON SCHEMAOutlookGeoCoordinates
JSON SCHEMAPatternedRecurrence
JSON SCHEMAMicrosoft Exchange Person
JSON SCHEMAPersonCollectionResponse
JSON SCHEMAPersonType
JSON SCHEMAPhone
JSON SCHEMAPhysicalAddress
JSON SCHEMARecipient
JSON SCHEMARecurrencePattern
JSON SCHEMARecurrenceRange
JSON SCHEMAResponseStatus
JSON SCHEMAScheduleInformation
JSON SCHEMAScheduleItem
JSON SCHEMAScoredEmailAddress
JSON SCHEMATimeConstraint
JSON SCHEMATimeSlot
JSON SCHEMAWebsite
JSON SCHEMAWorkingHours
JSON SCHEMAScroll within the panel for all 52 ·
JSON Structure 1
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 Exchange Structure
JSON STRUCTURESecurity 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.
Resources
Every other property we hold for Microsoft Exchange — 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 7
Reference material describing how the API behaves
Scroll within the panel for all 7 ·
Agent Surfaces 4
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 23
Pagination, idempotency, versioning, errors, and events
Scroll within the panel for all 23 ·
Build 5
SDKs, sample code, and the tooling you integrate with
Access & Security 6
Authentication, authorization, and security posture
Operate 5
Status, limits, changes, and where to get help
Commercial 3
Pricing, plans, and the legal terms of use
Company 2
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-exchange · machine-readable index on apis.io