Documentation
DocxAPI documentation
One HTTP request turns Markdown, HTML or JSON into a Word document or into native WordPress blocks. Same input, same API key, two destinations.
Reading this with an AI agent?
The entire documentation lives in one Markdown file, built to be fetched and read by an LLM. Copy the prompt below and paste it into ChatGPT, Claude, Cursor or any agent with web access — it asks the agent to read the file before helping you.
How it works
You send content and get a document back. That is the whole model — there is a single endpoint, and everything else is a detail of how you want the file delivered.
Start where you are
Most people arrive here from one of two directions. Pick yours.
Two destinations
Both endpoints read the same three input formats and share one API key and one credit balance. Pick by where the content is going.
Three ways in
The input_type field decides how your content is read. Everything else stays identical between the two endpoints.
The 30-second version
If you already have an API key, this is the shortest path to a Word file:
curl -X POST https://api.searchops.io/v1/generate \
-H "Content-Type: application/json" \
-H "x-api-key: sk_live_YOUR_KEY" \
-d '{
"input_type": "markdown",
"content": "# Hello\n\nThis is **bold** text.",
"response_format": "file",
"filename": "hello"
}' \
--output hello.docxNo key yet? Sign in at the dashboard and create one. The free plan includes 20 documents per month — no credit card.