Does OfficeMaker have an API?

Yes. OfficeMaker provides REST document-generation endpoints and a public OpenAPI description at https://free.officemaker.ai/gpt/openapi.json. Paid tenants use authenticated document-service endpoints with create, merge and edit.

What is JSON to DOCX, XLSX or PPTX in OfficeMaker?

You send a structured JSON payload that matches the live document schema. OfficeMaker returns a native Word, Excel or PowerPoint file. That is schema-led generation, not pasting HTML into an Office container.

Where is the OfficeMaker OpenAPI document?

The free-tier OpenAPI file is published at https://free.officemaker.ai/gpt/openapi.json. Paid tenants use authenticated document-service hosts for create, merge and edit.

Do I need an API key for the free sandbox?

The public free host at free.officemaker.ai does not require an API key for the published schema-led create surface. It is rate-limited and does not include merge, edit, macros or conversion.

Developers

Document generation API

OfficeMaker, operated by AI Build Group Ltd, exposes REST document-generation endpoints so your application can create native Word, Excel and PowerPoint files from JSON. A public OpenAPI document describes the free sandbox. Paid tenants add authenticated merge and edit.

Direct answer

The free REST create call uses document_type, file_name and document_json. document_json is one JSON string. An MCP create tool takes documentJson as an object. Both return a native Office file. Paid hosts add authenticated merge and edit.

What the API does

Fetch the live schema for Word, Excel or PowerPoint, validate a payload, then create a native Office file. That JSON-to-DOCX, JSON-to-XLSX and JSON-to-PPTX path is the same stack the product UI uses.

The free host at free.officemaker.ai does not require an API key for the published create/schema surface. Paid document-service hosts require authentication and expose create, merge and edit.

How a typical call works

GET the schema for the document type
Optionally run gap analysis on a draft payload
POST a structured create request
Receive or poll for the generated Office file and preview metadata

OpenAPI and portal

The free-tier OpenAPI file is at https://free.officemaker.ai/gpt/openapi.json. After you sign in, the document-service portal at docs.officemaker.ai/portal has schema-led guides for the same verbs.

MCP is the agent-oriented companion to this REST surface. Use REST from your backend; use MCP from an agent runtime that already speaks the protocol.

The free REST create call and an MCP tool call are not the same JSON. Checked against OpenAPI 1.1.5 at https://free.officemaker.ai/gpt/openapi.json on 4 November 2026, POST /gpt/v1/create-document requires document_type, file_name and document_json. document_type is word, excel or powerpoint. document_json is one JSON string, not a nested object. The published Word example uses file_name hello-world and a string whose root type is document, with blocks under content.children. A successful create publishes documentDownloadUrl as the file link. This page does not invent a sample response body.

An MCP create tool takes documentJson as an object. The Word example on this site was created that way: document type word, root type document, then a downloadable DOCX. Excel and PowerPoint use the same REST field names with document_type excel or powerpoint. Their inner JSON must match the live schema for that family. PowerPoint’s inner root type is powerpoint, not presentation.

Evidence behind the API claims

The API claims on this page are backed by the live OpenAPI description, the public free-tier code examples and the same schema-led document service exposed through MCP. These are stronger citation surfaces than repeating the same feature claim in another FAQ.

Claim. The OfficeMaker API creates native Word, Excel and PowerPoint files from structured JSON.

Mechanism. Applications fetch the live document schema, submit a schema-valid payload and the document-service middleware constructs the Office file.

Evidence. Public OpenAPI document

Limitation. The public free surface is intentionally narrower than authenticated paid document-service operations.

Limitations

Do not send secrets in document payloads. The free sandbox is rate-limited and does not include macros, conversion, merge or edit. Exact paid quotas depend on the organisation plan and are shown after sign-in rather than invented here.

Open developer resources · Create an account · Free tier OpenAPI (JSON) · Document service portal

Questions

Does OfficeMaker have an API?: Yes. OfficeMaker provides REST document-generation endpoints and a public OpenAPI description at https://free.officemaker.ai/gpt/openapi.json. Paid tenants use authenticated document-service endpoints with create, merge and edit.
What is JSON to DOCX, XLSX or PPTX in OfficeMaker?: You send a structured JSON payload that matches the live document schema. OfficeMaker returns a native Word, Excel or PowerPoint file. That is schema-led generation, not pasting HTML into an Office container.
Where is the OfficeMaker OpenAPI document?: The free-tier OpenAPI file is published at https://free.officemaker.ai/gpt/openapi.json. Paid tenants use authenticated document-service hosts for create, merge and edit.
Do I need an API key for the free sandbox?: The public free host at free.officemaker.ai does not require an API key for the published schema-led create surface. It is rate-limited and does not include merge, edit, macros or conversion.