1 creditStamp PDF API — text, image or Bates numbering
Text, an image, or sequential Bates numbers — nine anchors or exact coordinates, with opacity and rotation.
Stamp places exactly one of `text`, an uploaded `stamp_image`, or sequential `bates: {prefix, start, digits}` numbering onto each page in `pages` (default: every page), at one of nine anchors (`top-left` through `bottom-right`, plus `center`) or exact `x`/`y` coordinates in mm, with `opacity`, `rotation` (0/90/180/270) and, for text, `font_size`.
How does the Stamp PDF API work?
One HTTP request from any language. Every ASHDOCS endpoint uses the same X-API-Key header.
curl -X POST 'https://api.ashdocs.com/api/v2/tools/pdf-stamp' \
-H 'X-API-Key: ash_live_...' \
-F 'file=@document.pdf' -F 'options={"text":"CONFIDENTIAL","anchor":"bottom-right","opacity":0.5}'Common use cases
- →Adding a CONFIDENTIAL or DRAFT watermark stamp
- →Bates-numbering a document set for legal production
- →Placing a company logo in a page corner
Frequently asked questions
How much does the Stamp PDF API tool cost?+
1 credit per successful call. Sandbox keys (prefix ash_test_) run the tool end-to-end without ever consuming credits — use them in CI or for tuning.
What is the endpoint URL for this tool?+
The endpoint is documented in the curl example on this page. All ASHDOCS endpoints share the base URL https://www.ashdocs.com and require an X-API-Key header.
Can I run this tool inside Make, Zapier, or n8n?+
Yes — through each platform's built-in HTTP mechanism (Make's HTTP module, Webhooks by Zapier, n8n's HTTP Request node). Nothing to install: point it at this exact endpoint with your X-API-Key header. See /integrations/make, /integrations/zapier or /integrations/n8n for step-by-step setup.
Does this tool support batch or scheduled runs?+
Yes. POST /api/v1/batch runs any tool over up to 50 files with a single credit ledger entry, and pipeline schedules let you trigger the same tool on a cron. Both are documented in /docs.