write_pdfa4f.json
The JSON file of the “A PDF/A-4f Statement with Its Data Attached” example. A statement of account on the fourth part of the archival standard, carrying the same figures as an XML file a program reads without anybody retyping them.
This file is a request: an application sends it over the network to the server, which creates the PDF and sends it back. It creates the same page as the Rust and Python versions of this example. A request names every file it uses, never its content; the call carries the request and the files together. A font the server already holds, such as DejaVuSans, is named with nothing attached. Send the request to the address the API page gives.
This request names files it does not carry: statement. Each one travels beside the request, in the same call, as a supplied part named exactly as the request names it here — the description says which name plays which role, so you name your files as you like. A request naming a file the call carries nothing of is refused.
What This Example Is For
A statement of account is checked by a person and booked by a program. When the figures exist only on the page, somebody types them into the accounts, and a figure typed is a figure that can be typed wrong.
What This Example Shows
- A statement of account for May 2026: two lines and the amount due.
- The same statement attached inside the file as XML.
- Written on PDF 2.0, as the fourth part requires.