Developer API

The PDF tagging API for accessibility.

The same PDF/UA tagging engine as the web app, as a PDF accessibility API. Send a key, submit a PDF, and get a tagged, accessible PDF back.

Create an API keyAPI reference
Base api.pdf-tagger.comAuth Bearer keyRate 120 / min
quickstart.sh
# 1 — get a presigned upload, then PUT your PDF to the returned URL
curl -X POST https://api.pdf-tagger.com/v1/uploads \
  -H "Authorization: Bearer sk_live_..." \
  -H "Content-Type: application/json" \
  -d '{"filename":"report.pdf"}'

# 2 — submit the job (returns a job id)
curl -X POST https://api.pdf-tagger.com/v1/jobs \
  -H "Authorization: Bearer sk_live_..." \
  -H "Content-Type: application/json" \
  -d '{"key":"<key from step 1>","options":{"ocr":true,"embed_fonts":true}}'

Four steps to a tagged PDF

Jobs run asynchronously — poll for status, or let a webhook tell you.

01

Upload

Get a presigned URL and send the PDF straight to storage.

02

Submit

Start a job, with options for OCR and font embedding.

03

Poll or listen

Check the job's status, or receive a signed webhook when it finishes.

04

Download

Fetch a short-lived link to the tagged, accessible PDF.

The endpoints

Full reference →
POST/v1/uploadsPresigned upload for a PDF
POST/v1/jobsSubmit a tagging job
GET/v1/jobs/{id}Check a job's status
GET/v1/jobs/{id}/resultDownload the tagged PDF

Base URL https://api.pdf-tagger.com

Built for integration

✓

Per-job options

OCR scanned pages; embed fonts safely.

✓

Signed webhooks

HMAC-signed callbacks you can verify.

✓

OpenAPI 3.1 spec

Browse the reference; generate a client.

✓

Keys & webhooks dashboard

Manage keys and webhooks, see recent jobs.

1 credit / page

API jobs draw from the same credit balance as the web app, under the same plans. There is no separate API subscription.

Start with a key

Create an API key on the Developers page, then submit your first PDF with a single request.

Create an API keyAPI reference