Generate DOCX or PDF from a stored OpenXML template.

Overview

Generate DOCX or PDF from a stored OpenXML template. API clients must be tenant-aware, permission-aware, and capable of handling both JSON and binary responses.

Key points

• POST XML plus owner and template name or UUID.
• Use asPdf to request conversion.
• Use metadata to request JSON and base64.
• Composite templates must have a current compiled package.
• The package endpoint accepts a validated literal OpenXML manifest.

Endpoints

Example

{
  "owner": "<instance-uuid>",
  "uuid": "<template-uuid>",
  "xml": "<data>...</data>",
  "asPdf": false,
  "metadata": true
}

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. Send authentication and instance headers.
2. Validate the request body before transmission.
3. Inspect HTTP status, content type, and structured errors.
4. Log non-sensitive identifiers needed to reproduce failures.

Client requirements

• Check the HTTP status before processing the body.
• Check Content-Type before deciding whether the response is JSON, DOCX, or PDF.
• Do not log authentication tokens or complete client document data.
• Preserve the instance context through every Feradel service-to-service call.
• Treat validation and compilation errors as input or template defects rather than transient network failures.

Troubleshooting

A client treats an error as a file

Check HTTP status and Content-Type before writing the response body to disk.

The same request works in another tenant

Compare instance, owner, token permissions, and object UUIDs.

A route returns an unexpected envelope

The current controllers are not fully standardized; handle HTTP status and documented fields defensively.

Related documentation

• PDF Document and PDF Form API
• DOCX-to-PDF and XML API Reference
• API Integration Patterns and Examples

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.