Skip to content

PDF/UA · API documentation

Documentation

Add PDF/UA accessibility to your product with three predictable HTTP calls.
First successful request200 OK
POST/pdf/upload
{
  "successfulUploads": [
    "7c2f1e4a…e1c40"
  ]
}
  1. 01UploadcaseId
  2. 02Remediatecompleted
  3. 03DownloadPDF/UA

The integration contract

From API key to PDF/UA in three predictable steps

One base URL, one authentication header, and one case ID connect the entire workflow.

  1. POST/pdf/upload

    Upload

    Send one or more PDFs and receive a caseId for every accepted file.

  2. GET/job-status/{caseId}

    Track

    Poll a clear lifecycle from queued through running to a terminal status.

  3. GET/download/{caseId}

    Download

    Fetch the remediated document as a standard application/pdf response.

Copy, paste, ship

Your first upload is ready to run

Choose your stack. Every sample calls the same endpoint and returns the case ID used by the rest of the API.

  • Set ACCESSFUL_API_KEY
  • Place document.pdf in your working directory
  • Run the sample and keep successfulUploads[0]
Continue with the end-to-end quickstart
first-upload API
Terminal window
: "${ACCESSFUL_API_KEY:?Set ACCESSFUL_API_KEY first}"
curl --fail-with-body \
-X POST "https://api.accessful.de/api/v1/upload-service/pdf/upload" \
-H "X-API-Key: $ACCESSFUL_API_KEY" \
-F "files=@document.pdf"
200 OKsuccessfulUploads[0] → caseId

Choose your next step

Go from first request to production without hunting

Each path starts where you are and takes you directly to the detail you need.