Use case · Statements

The statement PDF API

Statements are long, tabular and unforgiving. A statement can run to forty pages of transactions, and every page needs the column headers repeated, the balance carried forward, and an accurate page count.

That is exactly what CSS paged media does well: thead repeats automatically across page breaks, counters produce Page N of M, and the totals are computed by your app, not by a layout engine's guesswork.

01How it works

Headers repeat automatically

Put transaction columns in a thead and Chrome repeats them on every page — no manual pagination in your code.

Page N of M

CSS counters give an accurate total page count even when the row count varies per customer.

Monthly at volume

Statement runs are bursty by nature. Submit them async and collect each finished document from a webhook rather than holding connections open.

02One request

request.sh

curl https://rendral.com/api/v1/pdf \
  -H "Authorization: Bearer sk_live_…" \
  -H "Content-Type: application/json" \
  -d '{ "html": "<table><thead>…</thead><tbody>…</tbody></table>",
        "async": true,
        "webhookUrl": "https://yourapp.com/hooks/statement-ready",
        "options": { "format": "Letter", "pageNumbers": true } }'

Frequently asked

Do table headers repeat on every page?

Yes — put them in a thead element and Chrome repeats them automatically across page breaks, which is the whole reason to render statements in a browser engine.

Can I show Page 3 of 12?

Yes. Use CSS counters in a footer, or enable pageNumbers for a standard centred counter.

How long can a statement be?

Long documents are fine. For hundred-page runs use async: true so the render happens in the background and you receive a webhook when it's ready.

How do I keep statements private?

Job output expires automatically, and signed URLs are time-limited — so a statement link can't be shared indefinitely or guessed.

A free tier, five endpoints, and SDKs for Node and Python.

Get an API key Read the docs →