snapdok

Guides · use case

Paper registration forms that match your online form

Every event meets the participant who cannot register online: no email account, a locked-down work machine, an organisation that wants paper on file. So someone makes a Word copy of the form — and from that day the two versions drift: a field gets added online, the paper copy misses it, and the data entry person curses both.

Generating the paper form from the web form ends the drift, because there is only one form. Ticket-type dropdowns stay dropdowns, consent checkboxes stay tickable, radio choices stay exclusive:

curl -X POST https://snapdok.io/v1/render \
  -H "Authorization: Bearer $SNAPDOK_KEY" \
  -H "Content-Type: application/json" \
  -d '{"url":"https://your-app.com/register","format":"pdf","pdf_forms":true,"pdf_form_only":true}' \
  --output registration.pdf

Because PDF fields keep their HTML names, a filled PDF that comes back can be read programmatically and pushed through the same handler your web form posts to — paper registrations land in the same database, without retyping.

Free keys need no card and include a monthly allowance — get one and try it on your own form. The docs list exactly which controls convert and how edge cases are handled.

Step-by-step guides