Data in, document out
A rendering API for the files a product has to produce anyway —
invoices, certificates, gift cards, tickets, labels.
PDF, JPG, PNG and WEBP from a template and a JSON body.
ireceipt.pro · Dashboard · API · SDK · Status
Every product eventually needs to hand a user a file. The invoice, the certificate, the ticket, the receipt. It is never the interesting part of the roadmap, and it reliably costs more than anyone budgeted: a headless browser somewhere, a font that renders differently in production, a render queue that falls over the week the newsletter goes out, and a template only one person knows how to edit.
IReceipt PRO is that part, as a service. You keep the design and the data. We keep the browsers, the fonts, the queue and the pager.
Pick a template. One from the public library, or your own design with dynamic fields — it is HTML, so it is a thing your designers can already edit.
Send your data. One REST call, or one line with the JS/TS SDK. Names, amounts, dates, QR codes.
import { IReceiptPRO } from '@ireceipt.pro/js';
const irp = new IReceiptPRO(process.env.IRECEIPT_API_KEY);
const pdf = await irp.createPdfFromPublicTemplate('invoice_universal_vzrt6k1s', invoice);Get the file back. PDF, JPG, PNG or WEBP, at whatever resolution you asked for — a thumbnail for a feed or something print-ready at full DPI, from the same template.
Every template in the library opens in the sandbox with real data before you write any code.
Invoices and receipts · certificates and diplomas · gift cards and vouchers · tickets and passes · scheduled reports and statements · email signatures · social and OG preview images · labels and price tags.
The list is not a feature matrix. It is one endpoint, and those are the things people have pointed it at.
Your templates and data stay yours. Private templates are private, access is scoped to your own API keys, and nothing you render becomes an example for someone else's landing page.
The failure modes are ours. No servers to size, no headless browser to keep patched, no rendering queue to babysit. When a font stops rendering at 3am it is our pager, which is the entire reason to buy this rather than build it. Current state is always at status.ireceipt.pro.
| Contents | |
|---|---|
| js | JS/TS SDK — @ireceipt.pro/js, dual CJS/ESM. MIT |
The SDK is the whole of the open source. The service, the dashboard, the landing and the design system are separate and closed, and are not linked from here — a link to a private repository is a 404 for everyone outside the organization, which is a poor first thing to hand a visitor.
Start with the FAQ. Bugs in the SDK specifically belong in its issue tracker; anything about your account, your templates or the API itself is better handled through the dashboard.
Found a way to read templates or documents that are not yours? Mail siarhei@dudko.dev rather than opening a public issue.
