Start from the PDF you already use
Keep the PDF layout your team already uses instead of rebuilding it in a heavier editor.
Map fields visually, preview a few rows, and export a full batch from the same PDF layout. When you need automation or integration, use the API.
Doqlo is built for teams that already know the document they need and want a lighter way to run repeatable PDF jobs.
This is the practical case for teams that want repeatable output without rebuilding the document every time.
Keep the PDF layout your team already uses instead of rebuilding it in a heavier editor.
Place fields in the web app, map them to CSV columns, and preview a few rows before the full export.
Set it up visually first, then use the API later when you need automation or system integration.
Doqlo fits teams working from a stable PDF layout, structured CSV rows, and repeated document runs. It is not a full document authoring suite.
Set up the mapping once in the web app. Export the batch when ready.
Start with the stable layout you already use.
Bring in the rows that drive each finished document.
Place fields once and check representative rows before the full run.
Run the batch in the web app first, then move the same process into the API when needed.
When one PDF layout needs fresh rows filled into it again and again, these are the kinds of jobs Doqlo fits well.
Fill customer details, totals, invoice numbers, and invoice QR or barcode fields into the same layout for every billing run.
Generate names, dates, IDs, codes, or QR fields on the same approved certificate layout from CSV rows.
Produce repeated customer, staff, or vendor letters from the same reviewed PDF layout.
Reuse the same internal form layout whenever a new batch of records is ready.
Turn order rows into consistent packing slips with item details, scannable barcodes, and QR fields without rebuilding the document.
Run recurring document batches from the same PDF layout whenever new rows are ready.
Start in the web app to set up the workflow visually. When you need automation or system integration later, use the API.
curl -X POST https://api.doqlo.com/v1/bulkfill/export-jobs \ -H "Authorization: Bearer $DOQLO_BF_EXPORT_API_KEY" \ -H "Idempotency-Key: $DOQLO_WEBHOOK_IDEMPOTENCY_KEY" \ -H "X-Request-Id: $DOQLO_WEBHOOK_REQUEST_ID" \ -F "[email protected];type=application/pdf" \ -F "[email protected];type=application/octet-stream" \ -F "[email protected];type=text/csv" \ -F "max_failed_row_percent=$DOQLO_MAX_FAILED_ROW_PERCENT" \ -F "delivery_mode=webhook" \ -F "webhook_url=$DOQLO_WEBHOOK_URL" \ -F "webhook_secret=$DOQLO_WEBHOOK_SECRET"Choose a plan when your recurring Bulk Fill volume grows beyond the free tier.
Use Sign for one-off signatures, dates, text, QR codes, barcodes, and other lightweight overlays on a single PDF. It stays free.
What teams usually want to know before they start.
No. Use the PDF you already have and place fields on top of it in the web app.
Bulk Fill is for repeatable PDF output from CSV. Sign is the free one-off tool for a single PDF.
No. Start in the web app to set up the workflow, map fields, and preview rows. Use the API later when another system needs to run the same workflow automatically.
Doqlo fits repeatable document jobs built from one stable PDF layout and structured rows, such as invoices, certificates, letters, internal forms, packing slips, and other recurring operational batches.
Yes. Preview a few representative rows first, then export the full batch when the output looks right.
No. It is built for repeatable output and lightweight signing, not full document authoring.