Generate documents that can be prepared for electronic signature.

Overview

Generate documents that can be prepared for electronic signature. FeraRender declares signing intent and returns manifest metadata; the signing system should resolve final coordinates after conversion to the signing PDF.

Key points

• Place stable anchor markers in the rendered document where signing fields belong.
• Embed a signature manifest in the DOCX package.
• Use recipient keys rather than hard-coded addresses where possible.
• Return signature metadata with the rendered document.
• Resolve final field positions after DOCX-to-PDF conversion.

Example

[[fs:client.signature]]
[[fs:client.date]]

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. Place stable anchors in the rendered document.
2. Embed and validate a versioned signature manifest.
3. Resolve recipient keys from trusted application data.
4. Generate the document, convert it, resolve anchors, and review the draft envelope.

Troubleshooting

A required field is not placed

Confirm the anchor survives conversion and the manifest refers to the same anchor and recipient key.

A recipient cannot be resolved

Supply trusted recipient data or valid name and email paths before creating or sending the envelope.

The field is offset incorrectly

Review anchor point, dimensions, offsets, and final PDF text extraction behavior.

Related documentation

• FeraRender Signature Manifest
• Signature Recipient Definitions
• Signature Field Definitions

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.