jstodocx.com API
Use the jstodocx.com API to create Word .docx files from controlled inputs. The API is useful for agents that need a downloadable DOCX without installing document-generation dependencies locally.
Read references/api.md when you need exact request schemas, examples, status codes, or response headers.
Workflow
- Choose one mode:
html: convert basic HTML headings, paragraphs, lists, and tables into DOCX.
js-source: archive JavaScript source text as a readable Word document. Do not treat this as code execution.
template: create a report, invoice, proposal, resume, or meeting-notes DOCX from structured fields.
- Send
POST https://jstodocx.com/api/v1/docx with content-type: application/json.
- If the endpoint returns
401, ask the user for an API key or use the browser-local website instead. Do not guess credentials.
- Save the binary response to a
.docx file.
- Verify the result when possible by checking the response
content-type, filename, and ZIP magic bytes PK.
Safety Rules
- Do not execute arbitrary JavaScript through this API. The
js-source mode treats JavaScript as text only.
- Do not send protected, confidential, or high-risk content unless the user explicitly confirms it is acceptable to send it to the API.
- Do not print, log, commit, or store API keys.
- Do not include raw user document content in logs or final summaries. Summarize mode, byte size, filename, and status instead.
- Do not claim pixel-perfect HTML fidelity. The API supports basic document formatting.
Minimal Example
curl -X POST "https://jstodocx.com/api/v1/docx" \
-H "content-type: application/json" \
--output release-plan.docx \
--data '{
"mode": "html",
"title": "Release Plan",
"html": "<h1>Release Plan</h1><p>Hello <strong>team</strong>.</p>"
}'
If the user provides an API key:
curl -X POST "https://jstodocx.com/api/v1/docx" \
-H "content-type: application/json" \
-H "authorization: Bearer $JSTODOCX_API_KEY" \
--output source-archive.docx \
--data '{
"mode": "js-source",
"title": "Widget Export Code",
"code": "function exportWidget() {\n return 42;\n}",
"options": { "lineNumbers": true }
}'
1---
2name: jstodocx-api
3description: Generate Microsoft Word DOCX files through the jstodocx.com API. Use when Codex needs to create or download .docx files from basic HTML, JavaScript source text, or controlled document template fields; when a user asks for HTML to DOCX, JS source to Word, or template-based DOCX generation via an API; or when integrating a lightweight Cloudflare Worker DOCX conversion endpoint into scripts, tests, or agent workflows.
4metadata:
5 source: https://skillmd.com/skills/aiskillstore/jstodocx-api
6---
7
8# jstodocx.com API
9
10Use the jstodocx.com API to create Word `.docx` files from controlled inputs. The API is useful for agents that need a downloadable DOCX without installing document-generation dependencies locally.
11
12Read [references/api.md](references/api.md) when you need exact request schemas, examples, status codes, or response headers.
13
14## Workflow
15
161. Choose one mode:
17 - `html`: convert basic HTML headings, paragraphs, lists, and tables into DOCX.
18 - `js-source`: archive JavaScript source text as a readable Word document. Do not treat this as code execution.
19 - `template`: create a report, invoice, proposal, resume, or meeting-notes DOCX from structured fields.
202. Send `POST https://jstodocx.com/api/v1/docx` with `content-type: application/json`.
213. If the endpoint returns `401`, ask the user for an API key or use the browser-local website instead. Do not guess credentials.
224. Save the binary response to a `.docx` file.
235. Verify the result when possible by checking the response `content-type`, filename, and ZIP magic bytes `PK`.
24
25## Safety Rules
26
27- Do not execute arbitrary JavaScript through this API. The `js-source` mode treats JavaScript as text only.
28- Do not send protected, confidential, or high-risk content unless the user explicitly confirms it is acceptable to send it to the API.
29- Do not print, log, commit, or store API keys.
30- Do not include raw user document content in logs or final summaries. Summarize mode, byte size, filename, and status instead.
31- Do not claim pixel-perfect HTML fidelity. The API supports basic document formatting.
32
33## Minimal Example
34
35```bash
36curl -X POST "https://jstodocx.com/api/v1/docx" \
37 -H "content-type: application/json" \
38 --output release-plan.docx \
39 --data '{
40 "mode": "html",
41 "title": "Release Plan",
42 "html": "<h1>Release Plan</h1><p>Hello <strong>team</strong>.</p>"
43 }'
44```
45
46If the user provides an API key:
47
48```bash
49curl -X POST "https://jstodocx.com/api/v1/docx" \
50 -H "content-type: application/json" \
51 -H "authorization: Bearer $JSTODOCX_API_KEY" \
52 --output source-archive.docx \
53 --data '{
54 "mode": "js-source",
55 "title": "Widget Export Code",
56 "code": "function exportWidget() {\n return 42;\n}",
57 "options": { "lineNumbers": true }
58 }'
59```