Stamp page numbers on every page of a PDF.
PDF Page Numbers stamps a page number on every page of a PDF, uploaded or fetched from a URL, and returns a download link to the numbered file. Choose the corner or edge and the font size. Paid plans can also set a label format such as Page 3 of 12, the starting number, and skip a cover page.
Try it — live request, no key required
No key required to try it. Get a key to use it in your app.
{
"status": "ok",
"error": null,
"data": {
"pdfName": "5c9f95f9-9719-47c3-a923-be3bc1f1dc91.pdf",
"pageCount": 2,
"numberedPages": 2,
"position": "bottom-center",
"format": "Page {page} of {total}",
"startAt": 1,
"lastLabel": "Page 2 of 2",
"size": 6218,
"expires": 1792230037933,
"downloadURL": "https://storage.googleapis.com/apiverve/APIData/pdfpagenumbers/5c9f95f9-9719-47c3-a923-be3bc1f1dc91.pdf?GoogleAccessId=635500398038-compute%40developer.gserviceaccount.com&Expires=1792230037&Signature=a2sCOtSuSIIEWobe8wq5iHcCdqlJMXhrHE9ewxXsf7qrNBK3NHtxrQYk%2Fn1Jpr08aQBVtJclbKX6CFqRigV2IL4suv%2F%2B8WF9LRX%2BhY%2Frhvkw9RfdydlsvALhpPxnxv547eShgBIsuwvEOPFry%2F1J%2FCvt3X%2BT8Iwpz9EtJJVKH8C3u8u26%2FlNjj7XcRCqx6hcVIWvkJEVuZfMQUjlcbtF4IOwvITwlIQW9ChPzMIlXdXu2amBIy9PinQoKsdVopBfTre4W%2BTH6%2BgynWlvnJAHmxM6mWdfLQxTjCyFzdT4ZmJuq%2BRM36d41N62KxiTGyP1cs0YJECt36nI3a7FTzUOrA%3D%3D"
}
}
About the PDF Page Numbers API
Numbers are drawn in Helvetica as real PDF text, so the rest of the document is untouched. Rotated pages are handled, so the number sits in the chosen corner the right way up as the page is displayed. Each call accepts one PDF of up to 10 MB and 300 pages.
What people use it for
- Generated Reports
- Number the pages of reports and exports produced by other tools that leave them unnumbered.
- Legal and Compliance
- Add Page X of Y labels to contracts and filings before they are signed or submitted.
- Merged Documents
- Number a document after merging several PDFs so the combined file reads as one.
- Print and Publishing
- Paginate manuscripts, handouts and booklets, skipping the cover page.
Ways to call it
One endpoint, many ways in — REST with JSON, XML, YAML and CSV, plus GraphQL and an MCP interface for AI agents.
- JSON
- Default REST response
- XML
- Markup format
- YAML
- Human-readable
- CSV
- Tabular export
- GraphQL
- Query language
- MCP
- For AI agents
Other ways to use PDF Page Numbers
Same data, same APIVerve account, same credit balance — one key works on all of them.
How many PDFs does the Starter plan cover?
What can I customise on the Free plan?
Where can the page number go?
What are the limits per call?
How long is the numbered file kept?
Request parameters — POST /v1/pdfpagenumbers
Sent as JSON in the request body. Premium parameters are accepted on every plan but only take effect on plans that include them. Anything not listed here is dropped rather than passed through.
Optional
| Parameter | Type | Example | Description |
|---|---|---|---|
pdfOptional | string | The PDF file to number (up to 10 MB and 300 pages), or a public PDF URL url | |
positionOptional | string | bottom-center | Where to place the numberbottom-centerbottom-rightbottom-lefttop-centertop-righttop-leftdefault bottom-center |
fontSizeOptional | number | 10 | Font size in points, from 6 to 36 default 10 · range 6-36 |
formatOptionalPremium | string | Page {page} of {total} | Label template containing {page}, and optionally {total}, such as Page {page} of {total} |
startAtOptionalPremium | integer | 1 | Number for the first numbered page range 0-100000 |
skipFirstOptionalPremium | boolean | false | Leave the first page (a cover) unnumbered |
curl -X POST "https://api.apiverve.com/v1/pdfpagenumbers" \
-H "x-api-key: YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{"position":"bottom-center","fontSize":10,"format":"Page {page} of {total}","startAt":1,"skipFirst":false}'Authentication
Send your key in the x-api-key header. That is the only auth step — no token exchange, and no per-endpoint scope to configure.
| Header | When | Value |
|---|---|---|
x-api-keyRequired | Every request | Your API key. Header names are case-insensitive, so X-API-Key is the same header. |
AuthorizationAlternate | Instead of the above | Bearer <key> — for clients that only expose bearer auth. Resolves to the same account and the same billing. |
content-typeRequired | POST body | application/json |
A 401 means the key is missing, invalid or expired. A 403 means the key is valid but not permitted here — blocked by a key restriction or an IP allow-list. Running out of credits is a 429.
Response — POST /v1/pdfpagenumbers
Every APIVerve endpoint returns the same three top-level keys, so one response handler covers your whole integration: status, error and data. Only data changes shape.
{
"status": "ok",
"error": null,
"data": {
"pdfName": "5c9f95f9-9719-47c3-a923-be3bc1f1dc91.pdf",
"pageCount": 2,
"numberedPages": 2,
"position": "bottom-center",
"format": "Page {page} of {total}",
"startAt": 1,
"lastLabel": "Page 2 of 2",
"size": 6218,
"expires": 1792230037933,
"downloadURL": "https://storage.googleapis.com/apiverve/APIData/pdfpagenumbers/5c9f95f9-9719-47c3-a923-be3bc1f1dc91.pdf?GoogleAccessId=635500398038-compute%40developer.gserviceaccount.com&Expires=1792230037&Signature=a2sCOtSuSIIEWobe8wq5iHcCdqlJMXhrHE9ewxXsf7qrNBK3NHtxrQYk%2Fn1Jpr08aQBVtJclbKX6CFqRigV2IL4suv%2F%2B8WF9LRX%2BhY%2Frhvkw9RfdydlsvALhpPxnxv547eShgBIsuwvEOPFry%2F1J%2FCvt3X%2BT8Iwpz9EtJJVKH8C3u8u26%2FlNjj7XcRCqx6hcVIWvkJEVuZfMQUjlcbtF4IOwvITwlIQW9ChPzMIlXdXu2amBIy9PinQoKsdVopBfTre4W%2BTH6%2BgynWlvnJAHmxM6mWdfLQxTjCyFzdT4ZmJuq%2BRM36d41N62KxiTGyP1cs0YJECt36nI3a7FTzUOrA%3D%3D"
}
}
Response fields
Paths are relative to data. Premium fields are absent rather than zeroed on plans that do not include them, so check for presence instead of comparing to 0.
| Field | Type | Example | Description |
|---|---|---|---|
pdfName | string | "5c9f95f9-9719-47c3-a923-be3bc1f1dc91.pdf" | File name of the numbered PDF |
pageCount | number | 2 | Pages in the PDF |
numberedPages | number | 2 | Pages that received a number |
position | string | "bottom-center" | Where the numbers were placed |
format | string | "Page {page} of {total}" | The label template used |
startAt | number | 1 | The number given to the first numbered page |
lastLabel | string | "Page 2 of 2" | The label on the last page, such as Page 12 of 12 |
size | number | 6218 | Size of the numbered PDF in bytes |
expires | number | 1792230037933 | When the download link expires (Unix time in milliseconds) |
downloadURL | string | "https://storage.googleapis.com/apiverve/APIData/pdfpagenumbers/5c9f95f9-9719-47c3-a923-be3bc1f1dc91.pdf?GoogleAccessId=635500398038-compute… | Signed link to download the numbered PDF, valid for 2 days |
Response headers
Every response carries your balance, so your own code always knows where it stands without polling anything. All four are exposed to browsers through CORS.
| Header | What it carries |
|---|---|
x-api-remaining-credits | Credits left in the current cycle |
x-api-credits-used | Credits spent in the current cycle |
x-api-max-credits | The allowance for the cycle |
x-api-version | Version of the endpoint that answered |
Errors
Read the HTTP status first, then error for the specific reason. The body names the parameter that has to change.
| Status | Meaning | What to do |
|---|---|---|
400 | Input was rejected | Read error; it names the parameter that has to change. |
401 | Key missing or invalid | Check the header name and the key value. |
403 | Key valid, but not permitted here | A key restriction or an IP allow-list — never a bad key. |
429 | Rate limited, or out of credits | Read error to tell them apart, then back off or top up. |
What a call costs — 10 credits per call
Credits are shared across every APIVerve API — one balance, one key, one bill. Failed requests never count against it, so a rejected input costs nothing.
| Plan | Per month | Credits | PDF Page Numbers calls | Per 1,000 calls |
|---|---|---|---|---|
| Free | Free | 200 | 20 | Free |
| Starter | $29.99 | 200,000 | 20,000 | $1.50 |
| Pro | $99.99 | 1,000,000 | 100,000 | $1.00 |
| Mega | $299.99 | 4,000,000 | 400,000 | $0.75 |
Calls are what the credits buy at this API's rate — spend them here, on any of the other APIs, or across both. Nothing is reserved per endpoint.
Call it from cURL — POST /v1/pdfpagenumbers
No SDK to install — this is a plain HTTPS call to /v1/pdfpagenumbers with your key in the x-api-key header. Swap in a real key and it runs as-is.
curl "https://api.apiverve.com/v1/pdfpagenumbers" \
-H "x-api-key: YOUR_API_KEY"Resources
Call it from Node.js — POST /v1/pdfpagenumbers
No SDK to install — this is a plain HTTPS call to /v1/pdfpagenumbers with your key in the x-api-key header. Swap in a real key and it runs as-is.
const res = await fetch("https://api.apiverve.com/v1/pdfpagenumbers", {
headers: { "x-api-key": "YOUR_API_KEY" },
});
const { data } = await res.json();
console.log(data);Resources
Call it from Python — POST /v1/pdfpagenumbers
No SDK to install — this is a plain HTTPS call to /v1/pdfpagenumbers with your key in the x-api-key header. Swap in a real key and it runs as-is.
import requests
res = requests.get(
"https://api.apiverve.com/v1/pdfpagenumbers",
headers={"x-api-key": "YOUR_API_KEY"},
)
print(res.json()["data"])Resources
Call it from C# / .NET — POST /v1/pdfpagenumbers
No SDK to install — this is a plain HTTPS call to /v1/pdfpagenumbers with your key in the x-api-key header. Swap in a real key and it runs as-is.
using var client = new HttpClient();
client.DefaultRequestHeaders.Add("x-api-key", "YOUR_API_KEY");
var json = await client.GetStringAsync("https://api.apiverve.com/v1/pdfpagenumbers");
Console.WriteLine(json);Resources
Call it from Go — POST /v1/pdfpagenumbers
No SDK to install — this is a plain HTTPS call to /v1/pdfpagenumbers with your key in the x-api-key header. Swap in a real key and it runs as-is.
req, _ := http.NewRequest("GET", "https://api.apiverve.com/v1/pdfpagenumbers", nil)
req.Header.Set("x-api-key", "YOUR_API_KEY")
res, _ := http.DefaultClient.Do(req)
defer res.Body.Close()
body, _ := io.ReadAll(res.Body)
fmt.Println(string(body))Resources
Call it from PHP — POST /v1/pdfpagenumbers
No SDK to install — this is a plain HTTPS call to /v1/pdfpagenumbers with your key in the x-api-key header. Swap in a real key and it runs as-is.
$ch = curl_init("https://api.apiverve.com/v1/pdfpagenumbers");
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
curl_setopt($ch, CURLOPT_HTTPHEADER, ["x-api-key: YOUR_API_KEY"]);
$response = curl_exec($ch);
echo $response;Resources
Call it from Ruby — POST /v1/pdfpagenumbers
No SDK to install — this is a plain HTTPS call to /v1/pdfpagenumbers with your key in the x-api-key header. Swap in a real key and it runs as-is.
require "net/http"
uri = URI("https://api.apiverve.com/v1/pdfpagenumbers")
req = Net::HTTP::Get.new(uri)
req["x-api-key"] = "YOUR_API_KEY"
res = Net::HTTP.start(uri.hostname, uri.port, use_ssl: true) { |h| h.request(req) }
puts res.bodyResources
Zero-code embed — one snippet, no backend
Drop an interactive PDF Page Numbers form onto any page. The widget calls the API for you, so no key ever appears in your markup and there is nothing to deploy.
Changelog — PDF Page Numbers API
Every change to this endpoint, newest first. Breaking changes ship as a new version and the previous one keeps serving — response fields are added, never removed or retyped in place, so an integration written against v1 keeps working.
Entries are picked up from dated catalog snapshots, so the first one appears after the next snapshot that moves something. A period where nothing changed produces no entry — silence is a valid changelog for the PDF Page Numbers API.
Documents
- HTML to PDF
- Invoice Generator
- PDF Merge
- PDF Page Numbers
- PDF to Text
- Website to PDF