Retrieve the available fields from a supplied or stored PDF form.

Overview

Retrieve the available fields from a supplied or stored PDF form. 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

• Supply a direct PDF or form value, or identify a stored template.
• The service forwards the PDF to the configured renderer fields endpoint.
• Use the returned field list when building mappings.
• An empty or missing form produces a not-found response.
• Do not assume visible labels equal internal PDF field names.

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

• Fill a PDF Form
• OpenXML Package Manifest Reference
• Literal OpenXML Package Generation

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.