Bulk-fill PDFs programmatically
This is bulk fill for developers: drive Emboss from your own application. Detect a form's fields once, then fill it for every record in your dataset. Each fill is an independent API call, so a batch is just a loop you control. Fan out as wide as your throughput needs and collect the finished PDFs as they complete. (Prefer no code? See batch fill from a spreadsheet.)
Detect once, fill many
Field detection happens when you create the form. Every subsequent fill reuses that contract, so a thousand-record run pays the detection cost once and the fill cost per document, which is predictable and parallel-friendly.
Running a batch in code
Iterate your records, issue one fill request per record, and write each returned PDF to storage. Because requests are independent, you can run them concurrently and retry any single failure without touching the rest of the batch. You own the loop, the concurrency, and where the output lands.
Keeping it reliable
Track each fill by its form and record id, poll or use webhooks for completion, and reconcile at the end. A failed document is isolated to its own call, so partial batches recover cleanly.
Not a developer?
If your data lives in a spreadsheet and you'd rather not write code, batch fill from a spreadsheet does the same thing in your browser: upload one form and a CSV or Excel file and download a ZIP of filled PDFs. This page is the programmatic path for when you're building the run into your own system.