Architecture
Your frontend collects user intent (what to redact, which PDFs to merge, which certificate to use). Your backend sends the structured request to Forme’s API and returns the result./v1/* endpoints accept JSON and return PDF bytes (or JSON for rasterize). No cookies, sessions, or UI dependencies.
Custom Redaction UI
Build a UI where users draw boxes on a PDF preview, then send the coordinates to Forme:Custom Merge Workflow
Let users select and reorder PDFs, then merge:Programmatic Certification
Certify documents as part of an approval workflow:Preview Generation
Use rasterization to generate preview images for your own document viewer:Resource Management
List your templates, documents, and certificates programmatically:Self-Hosted
All operation endpoints (/v1/render, /v1/certify, /v1/redact, /v1/merge, /v1/rasterize) work on self-hosted instances. Point your application at your own Forme container and avoid external API calls entirely.
The only features that require the hosted API are: saved templates, saved certificates (certificateId), redaction templates (template slug), document storage, and resource listing.