Microsoft Outlook
Microsoft Outlook is a personal information manager and email client that is part of the Microsoft Office suite. It provides email, calendar, contact management, task management, and other productivity features.
Reference-quality API operations across every facet — a rich contract, published governance, transparent operations, and machine-readable commercial terms.
API Evangelist profiles Microsoft Outlook the way a machine reads it — 100 machine-readable artifacts across 4 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 Outlook scores 80.2/100 (exemplar), with a separate agent-readiness read of 77/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.
How we profile Microsoft Outlook
Each block below is one kind of artifact we hold for Microsoft Outlook. 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 4
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.
Outlook Add-ins API
JavaScript API for building Outlook add-ins that extend Outlook functionality with custom features, using the Office.js library and the Mailbox requirement set.
Microsoft Outlook Attachments API
Operations on message attachments
Microsoft Outlook Mail Folders API
Operations on mail folders in a user mailbox
Microsoft Outlook Messages API
Operations on email messages in a user mailbox
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.
Open Collections 1
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 Outlook Microsoft Graph Mail API
OPEN COLLECTIONArazzo Workflows 12
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 Outlook Archive Copy of a Message
Create an archive folder, copy a message into it, and read the copy back.
ARAZZOMicrosoft Outlook Build Folder Tree and Seed Draft
Create a parent folder, a child subfolder, and a seed draft inside the child.
ARAZZOMicrosoft Outlook Compose, Attach, and Send
Create a draft message, attach a file to it, and send the finished draft.
ARAZZOMicrosoft Outlook Draft, Refine, and Send
Create a draft, refine its body and importance, then send the polished draft.
ARAZZOMicrosoft Outlook File Message into New Folder
Create a mail folder, find a matching message, and move it into the folder.
ARAZZOMicrosoft Outlook Find and Forward
Find a message by subject, read it, then forward it to a new recipient.
ARAZZOMicrosoft Outlook Inspect and Remove Attachment
Find a message with attachments, inspect the first one, and delete it.
ARAZZOMicrosoft Outlook Large Attachment Upload Session
Draft a message and open an upload session for a large (3-150 MB) attachment.
ARAZZOMicrosoft Outlook Reorganize Folder
Create a destination folder, find a source folder by name, and move it under the destination.
ARAZZOMicrosoft Outlook Reply Draft with Attachment
Create a reply draft for a message, attach a file, and send the reply.
ARAZZOMicrosoft Outlook Review Folder and Mark Read
Open a mail folder, list its unread messages, and mark the top one as read.
ARAZZOMicrosoft Outlook Triage and Reply
List the newest messages, read the top one in full, and reply to its sender.
ARAZZOScroll within the panel for all 12 ·
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-outlook-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 Outlook 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 Outlook Finops
FINOPSFeatures 10
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 10 ·
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 Outlook Change Notifications
AsyncAPI specification for Microsoft Graph change notifications (webhooks) for Outlook mail resources. Enables real-time event-driven architecture by subscribing to changes in m...
ASYNCAPISemantic Vocabularies 2
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 Graph Mail Context
JSON-LDMicrosoft Outlook Context
JSON-LDSpectral 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 Outlook API Rules
SPECTRALMicrosoft Outlook API Rules
SPECTRALMicrosoft Outlook API Rules
SPECTRALJSON Schema 15
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.
AttachmentCollectionResponse
JSON SCHEMAAttachment
JSON SCHEMADateTimeTimeZone
JSON SCHEMAEmailAddress
JSON SCHEMAFollowupFlag
JSON SCHEMAInternetMessageHeader
JSON SCHEMAItemBody
JSON SCHEMAMailFolderCollectionResponse
JSON SCHEMAMailFolder
JSON SCHEMAMessageCollectionResponse
JSON SCHEMAMessage
JSON SCHEMAODataError
JSON SCHEMARecipient
JSON SCHEMAUploadSession
JSON SCHEMAMicrosoft Outlook Message
JSON SCHEMAScroll within the panel for all 15 ·
JSON Structure 14
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 Graph Mail Attachment Structure
JSON STRUCTUREMicrosoft Graph Mail Date Time Time Zone Structure
JSON STRUCTUREMicrosoft Graph Mail Email Address Structure
JSON STRUCTUREMicrosoft Graph Mail Followup Flag Structure
JSON STRUCTUREMicrosoft Graph Mail Internet Message Header Structure
JSON STRUCTUREMicrosoft Graph Mail Item Body Structure
JSON STRUCTUREMicrosoft Graph Mail Mail Folder Structure
JSON STRUCTUREMicrosoft Graph Mail Message Structure
JSON STRUCTUREMicrosoft Graph Mail O Data Error Structure
JSON STRUCTUREMicrosoft Graph Mail Recipient Structure
JSON STRUCTUREMicrosoft Graph Mail Upload Session Structure
JSON STRUCTUREScroll within the panel for all 14 ·
Examples 14
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.
Scroll within the panel for all 14 ·
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 Outlook Trust Center
SOC 1, SOC 2, SOC 3, ISO 27001, ISO 27017, ISO 27018, ISO 27701, ISO 42001, ISO 22301, CSA STAR Certification, CSA STAR Attestation, FedRAMP, FIPS 140-2, HIPAA / HITECH, HITRUST...
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 6
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.
Integrations 7
Pre-built integrations with other platforms tell you where this provider already fits in a stack.
Pre-built integrations with other platforms and tools.
Scroll within the panel for all 7 ·
Resources
Every other property we hold for Microsoft Outlook — 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 6
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 4
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 18
Pagination, idempotency, versioning, errors, and events
Scroll within the panel for all 18 ·
Build 5
SDKs, sample code, and the tooling you integrate with
Access & Security 6
Authentication, authorization, and security posture
Learn 1
Tutorials, courses, talks, and written guidance
Operate 5
Status, limits, changes, and where to get help
Commercial 2
Pricing, plans, and the legal terms of use
Company 1
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-outlook · machine-readable index on apis.io