Combine photos, scans or receipts into one PDF, one image per page, in the order sent. Here is the whole call in Node.js, with the output it produced when we ran it.
Before you start
An API key. Create a free account; it comes with free tokens every month. Put the key in an environment variable so it stays out of your code: export BLOODWEB_KEY=your_key
Node.js 18 or later. Nothing to install: fetch, FormData and Blob are built in. Save the file with the .mjs ending so await works at the top level.
The input files in the same folder: receipt1.jpg, receipt2.jpg. Use your own; those are the names the code expects.
The code
Save it as images-to-pdf.mjs and run node images-to-pdf.mjs.
// Node.js 18 or later: fetch, FormData and Blob are built in.
import { readFile, writeFile } from "node:fs/promises";
const form = new FormData();
form.append("files[]", new Blob([await readFile("receipt1.jpg")]), "receipt1.jpg");
form.append("files[]", new Blob([await readFile("receipt2.jpg")]), "receipt2.jpg");
const res = await fetch("https://bloodweb.net/api/v1/images-to-pdf", {
method: "POST",
headers: { Authorization: `Bearer ${process.env.BLOODWEB_KEY}` },
body: form,
});
if (!res.ok) throw new Error(`${res.status}: ${(await res.json()).error.message}`);
await writeFile("receipts.pdf", Buffer.from(await res.arrayBuffer()));
What you get
Tested 19 October 2026: this exact code ran against our test copy of the API, which runs the same service code as bloodweb.net, and produced this.
It writes receipts.pdf: a PDF, 2 pages, 79 KB.
Page 1 of the result.
Change the call
Every option the Images to PDF takes. Add or change them the same way as the ones in the code.
page: Paper size, or fit to make each page the size of its image. One of: A4, Letter, Legal, A5, fit.
margin: Margin in millimetres (ignored for fit).
quality: JPEG quality of the images inside the PDF.
If it fails
A failed call is not charged. The answer is JSON with an error object; the code above prints its message. The usual ones:
401missing_key or invalid_key: BLOODWEB_KEY is not set in the shell that runs the code, or the key was revoked.
415unsupported_type: the file is not a type this service reads. The type is read from the file itself, so renaming a file does not change it.
413file_too_large: the file is over the limit on the service page.
402insufficient_tokens: the balance does not cover the call. Top up in the dashboard.
429rate_limited: too many calls at once. Wait the seconds in the Retry-After header and send it again.
