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 Word Documents API

Operations for creating, opening, and managing Word documents

Microsoft Word Documents API is one of 19 APIs that Microsoft Word publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

This API exposes 14 JSON Schema definitions.

Tagged areas include Documents. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, authentication docs, an API reference, a JSON-LD context, a getting-started guide, and 14 JSON Schemas.

This API exposes 5 operations across 4 paths, and defines 7 schemas. It is described by OpenAPI 3.2.0, at version 1.0.

Requests are made against 2 base URLs: https://word.officeapps.live.com/api/v1, https://localhost:5000/api/v1.

5 operations 4 paths 7 schemas 1 DELETE1 GET3 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0
Base URL
https://graph.microsoft.com/v1.0
Authentication
OAuth 2.0
Resource Areas
1

Authentication & Security 1

Microsoft Word Documents API declares 1 security scheme for authenticating requests. It supports OAuth 2.0 (oauth2) using the authorizationCode flow, exposing 1 scope.

  • oauth2 — OAuth 2.0 via Microsoft Identity Platform for Office Add-ins.

Paths & Operations 5

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

Documents 5

Operations for creating, opening, and managing Word documents

POST
/documents
Microsoft Word Create Document
createDocument body → 201401
GET
/documents/{document-id}
Microsoft Word Get Document
getDocument 1 param → 200404
DELETE
/documents/{document-id}
Microsoft Word Delete Word Document
deleteWordDocument 1 param → 204404
POST
/documents/{document-id}/save
Microsoft Word Save Document
saveDocument 1 param → 204401
POST
/documents/{document-id}/convert
Microsoft Word Convert Document
convertDocument 1 param body → 200400

Schemas 7

The contract defines 7 schemas that model the data the API accepts and returns. The most detailed are WordDocument (8 properties), CreateDocumentRequest_2 (4 properties), Document (3 properties), ConvertRequest (1 property). Each schema is shown below with its type and property counts.

Document
object
Represents a Word document.
3 properties
ErrorResponse
object
Error response from the API.
1 property
CreateDocumentRequest
object
Request to create a new document.
1 property
WordDocument
object
Represents a Word document processed by the Open XML SDK.
8 properties
ErrorResponse_2
object
Error response from the API.
1 property
CreateDocumentRequest_2
object
Request to create a new document.
4 properties
ConvertRequest
object
Request to convert a document to another format.
1 property 1 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

microsoft-word-documents-api-openapi.yml Raw ↑

Other APIs Microsoft Word publishes across the network.

Word Automation Services (SharePoint)
Microsoft Word Body API
Microsoft Word Checkout API
Microsoft Word Comments API
Microsoft Word Content API
Microsoft Word Content Controls API
Microsoft Word Drive Items API
Microsoft Word Headers And Footers API
Microsoft Word Images API
Microsoft Word Paragraphs API
Microsoft Word Permissions API
Microsoft Word Properties API
Where this information came from

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