Rendral

Use case · Receipts

The receipt PDF API

The instant an order or payment succeeds, customers expect a clean receipt. Generating it should be one call in your webhook handler, not a rendering service you maintain.

Send your receipt HTML and get a PDF back immediately — small, fast, and safe to retry if your webhook fires twice.

01How it works

01

On the transaction

Render the receipt right in your payment webhook and attach it to the confirmation email.

02

Idempotent by order

Key the request by order ID so a re-delivered webhook returns the same receipt.

03

Compact and fast

Receipts are small documents — cached and returned in milliseconds on repeat.

02One request

request.sh
curl https://rendral.com/api/v1/pdf \
  -H "Authorization: Bearer sk_live_…" \
  -H "Idempotency-Key: order-88213" \
  -H "Content-Type: application/json" \
  -d '{ "html": "<h1>Receipt</h1>…" }' \
  -o receipt.pdf

Frequently asked

How do I avoid duplicate receipts?

Send an Idempotency-Key (for example the order ID). A repeated request returns the original receipt without re-rendering.

Is it fast enough for a checkout flow?

Yes — receipts are small, and identical requests are served from cache instantly.

Can I email the PDF directly?

Generate the PDF via the API, then attach the returned bytes in your existing email pipeline.

Start rendering in minutes.

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

Get an API keyRead the docs →