Create an editable DOCX from a literal package manifest without storing a template.

Overview

Create an editable DOCX from a literal package manifest without storing a template. Document formats have different failure modes. Confirm whether the workflow transforms data, fills an existing form, packages OpenXML, or only converts a file.

Key points

• Submit content to the package endpoint.
• Use literal parts only.
• Include every required OpenXML part.
• External relationships, macros, OLE, attached templates, and altChunk are prohibited.
• Unsafe paths and traversal are rejected.
• The result is returned as base64 DOCX metadata.

Example

{
  "name": "Agreement.docx",
  "xml": "<data/>",
  "package": "<root version=\"1\">...</root>"
}

Replace bracketed values with values issued for the target environment. Never place production tokens, API keys, or client data in screenshots or public examples.

Recommended procedure

1. Choose the exact PDF or DOCX workflow.
2. Validate the source template or file.
3. Submit representative data with the expected response mode.
4. Open the resulting file and verify layout, fonts, fields, and metadata.

Troubleshooting

The PDF is blank or malformed

Validate the transform output or field mapping before blaming the conversion engine.

Fonts or pagination differ

Install required fonts and test with the same conversion engine used in production.

Conversion fails for one file

Open and resave the source DOCX, remove unsupported content, and compare it with a known-good file.

Related documentation

• Convert DOCX to PDF
• Render DOCX as PDF or Metadata
• OpenXML Package Manifest Reference

Documentation source: feradelinc/feradel.render.api, reviewed against repository revision b2c3a710. Verify behavior against the deployed release before publishing exact routes, limits, or version requirements.