Rendral

Use case · Reports

The PDF report API

Analytics products and internal tools constantly need to export a view as a PDF report — for a client, a board deck, or a scheduled email.

Point the API at a report URL or send rendered HTML. For dashboards that draw charts client-side, wait for a selector before capture so nothing renders half-drawn.

01How it works

01

Wait for charts

Use waitForSelector or a delay so client-rendered charts and data finish before the PDF is produced.

02

Scheduled exports

Kick off a render from your cron job and email the resulting PDF — no browser to babysit.

03

Headers on every page

Add a running header/footer with the report title, date and page numbers.

02One request

request.sh
curl https://rendral.com/api/v1/pdf \
  -H "Authorization: Bearer sk_live_…" \
  -H "Content-Type: application/json" \
  -d '{ "url": "https://app.example.com/reports/42",
        "options": { "waitForSelector": "#chart.ready", "pageNumbers": true } }' \
  -o report.pdf

Frequently asked

My charts render client-side — will they show?

Yes. Set waitForSelector (or a delay) so the API waits until your charts signal ready before capturing.

Can I render an authenticated report page?

Send the fully-rendered HTML from your server, or a URL that includes a short-lived token — never long-lived secrets in the URL.

Can I add a title and page numbers?

Yes — supply a headerTemplate/footerTemplate, or set pageNumbers: true.

Start rendering in minutes.

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

Get an API keyRead the docs →