Microsoft Word
APIs for Microsoft Word document creation, manipulation, and automation across Microsoft 365 cloud services, Office Add-ins, SharePoint, and Open XML document processing.
Reference-quality API operations across every facet — a rich contract, published governance, transparent operations, and machine-readable commercial terms.
API Evangelist profiles Microsoft Word the way a machine reads it — 90 machine-readable artifacts across 19 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 Word scores 72.5/100 (exemplar), with a separate agent-readiness read of 71/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 Word
Each block below is one kind of artifact we hold for Microsoft Word. 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 19
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.
Word Automation Services (SharePoint)
Server-side document conversion and automation service for SharePoint. Supports batch conversion of Word documents to PDF, XPS, and other formats without user interaction.
Microsoft Word Body API
Operations on the document body content
Microsoft Word Checkout API
Operations for checking in and out files
Microsoft Word Comments API
Operations for managing comments and replies
Microsoft Word Content API
Operations for uploading and downloading file content
Microsoft Word Content Controls API
Operations for managing content controls
Microsoft Word Documents API
Operations for creating, opening, and managing Word documents
Microsoft Word Drive Items API
Operations for managing files and folders in OneDrive and SharePoint
Microsoft Word Headers And Footers API
Operations for managing headers and footers
Microsoft Word Images API
Operations for managing images in documents
Microsoft Word Paragraphs API
Operations for managing paragraphs in documents
Microsoft Word Permissions API
Operations for managing sharing and permissions on drive items
Microsoft Word Properties API
Operations for managing document properties
Microsoft Word Search API
Operations for searching files and folders
Microsoft Word Sections API
Operations for managing document sections
Microsoft Word Styles API
Operations for managing document styles
Microsoft Word Tables API
Operations for creating and managing tables
Microsoft Word Thumbnails API
Operations for retrieving file thumbnails
Microsoft Word Versions API
Operations for managing file version history
Scroll within the panel for all 19 ·
Postman Collections 3
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.
Microsoft Graph Word API
POSTMANMicrosoft Word Open XML SDK
POSTMANArazzo 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 Word Author Document from HTML
Create a blank Word document, insert HTML content into its body, and save it.
ARAZZOMicrosoft Word Browse Folder and Copy Document
List the documents in a folder and branch to copy the first item or report an empty folder.
ARAZZOMicrosoft Word Build Report Body
Insert a heading, add a data table, list the resulting paragraphs, and save the document.
ARAZZOMicrosoft Word Checkout Edit and Check In Document
Lock a Word document for editing, upload revised content, and check it back in with a comment.
ARAZZOMicrosoft Word Generate Document and Convert to PDF
Create a Word document with the Open XML SDK, add a paragraph and a table, then convert it to PDF.
ARAZZOMicrosoft Word Inspect Document and Export HTML
Read an Open XML document's structure, update its properties, list its paragraphs, and export it to HTML.
ARAZZOMicrosoft Word Organize Folder and Invite Reviewers
Create a project folder, upload a Word document into it, and invite reviewers with edit access.
ARAZZOMicrosoft Word Rename Move and Audit Document
Rename a Word document, move it to a new folder, and list its version history.
ARAZZOMicrosoft Word Resumable Upload Session
Open a resumable upload session for a large Word document and confirm the stored item afterward.
ARAZZOMicrosoft Word Search and Download Document
Search OneDrive for a Word document by name, confirm its metadata, and download its content.
ARAZZOMicrosoft Word Search Body and Tag Document
Search a document body for text, update the document properties, and save it.
ARAZZOMicrosoft Word Upload and Share Document
Upload a Word document to OneDrive, confirm its metadata, and generate an organization sharing link.
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-word-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 Word 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 Word Finops
FINOPSFeatures 8
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.
Document Creation
Programmatically create Word documents from templates or scratch using REST APIs or JavaScript.
Document Conversion
Convert Word documents to PDF, HTML, and other formats using server-side automation services.
Content Manipulation
Insert, edit, and format text, paragraphs, tables, images, and content controls in Word documents.
Collaboration
Track changes, manage comments, co-authoring sessions, and revision history through APIs.
Template Processing
Mail merge, document assembly, and template-based document generation for enterprise workflows.
Cloud Storage Integration
Access and manipulate Word documents stored in OneDrive, SharePoint, and Microsoft 365 cloud services.
Add-In Extensibility
Build custom Word add-ins with JavaScript APIs for task panes, content insertion, and document automation.
Open XML Processing
Low-level manipulation of Word document structure using the ECMA-376 Open XML standard.
Scroll within the panel for all 8 ·
Semantic Vocabularies 3
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.
Spectral Rules 2
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 Word API Rules
SPECTRALMicrosoft Word API Rules
SPECTRALJSON Schema 7
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.
DriveItem
JSON SCHEMAPermission
JSON SCHEMAComment
JSON SCHEMAContentControl
JSON SCHEMAParagraph
JSON SCHEMATable
JSON SCHEMAOpenXmlDocumentProperties
JSON SCHEMAScroll within the panel for all 7 ·
JSON Structure 7
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.
Graph Api Drive Item Structure
JSON STRUCTUREGraph Api Permission Structure
JSON STRUCTUREJavascript Api Comment Structure
JSON STRUCTUREJavascript Api Content Control Structure
JSON STRUCTUREJavascript Api Paragraph Structure
JSON STRUCTUREJavascript Api Table Structure
JSON STRUCTUREOpen Xml Sdk Document Properties Structure
JSON STRUCTUREScroll within the panel for all 7 ·
Examples 7
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.
Graph Api Drive Item Example
EXAMPLEGraph Api Permission Example
EXAMPLEJavascript Api Table Example
EXAMPLEScroll within the panel for all 7 ·
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 Word Trust Center
SOC 1 Type 2, SOC 2 Type 2, SOC 3, ISO 27001, ISO 27017, ISO 27018, FedRAMP, FIPS 140-2, HIPAA
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.
Automated Report Generation
Generate standardized reports from data sources using templates and API-driven document creation.
Contract and Legal Document Assembly
Assemble legal documents by merging clauses, terms, and client data into Word templates.
Document Review Workflows
Automate review cycles with tracked changes, comments, and approval workflows via APIs.
Bulk Document Processing
Process large volumes of Word documents for format conversion, content extraction, or metadata updates.
Custom Business Add-Ins
Build task pane add-ins that connect Word to CRM, ERP, or other business systems for data insertion.
Compliance Document Management
Ensure regulatory compliance by automating document formatting, metadata tagging, and archiving.
Integrations 6
Pre-built integrations with other platforms tell you where this provider already fits in a stack.
Pre-built integrations with other platforms and tools.
Microsoft SharePoint
Store, manage, and collaborate on Word documents through SharePoint document libraries and workflows.
Microsoft OneDrive
Access and sync Word documents via OneDrive cloud storage through Microsoft Graph APIs.
Microsoft Teams
Collaborate on Word documents directly within Teams channels and chat conversations.
Microsoft Power Automate
Automate Word document workflows including creation, conversion, and approval routing with Power Automate flows.
Microsoft Copilot
AI-powered document creation, editing, and summarization through Copilot agents with add-in actions.
Azure Active Directory
OAuth 2.0 authentication and authorization for secure API access through Microsoft Identity Platform.
Resources
Every other property we hold for Microsoft Word — 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
Agent Surfaces 4
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 19
Pagination, idempotency, versioning, errors, and events
Scroll within the panel for all 19 ·
Build 4
SDKs, sample code, and the tooling you integrate with
Access & Security 6
Authentication, authorization, and security posture
Learn 2
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 2
The organization behind the API
Other 4
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/microsoft-word · machine-readable index on apis.io