Auto-tag PDFs via API

Use the /accessibility/autotag endpoint below to tag PDFs for accessibility workflows.

Multipart upload request

Terminal window
curl -X POST "https://api.nutrient.io/accessibility/autotag" \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -F "file=@input.pdf" \
  -F 'data={"conformance":"pdfua-1"};type=application/json' \
  --fail \
  -o output-tagged.pdf

Remote file request

Terminal window
curl -X POST "https://api.nutrient.io/accessibility/autotag" \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "file": { "url": "https://example.com/input.pdf" },
    "conformance": "pdfua-1"
  }' \
  --fail \
  -o output-tagged.pdf

Use the pipeline pattern below in production workflows.

  • Validate source PDF quality and detect obvious corruption.
  • Run auto-tagging.
  • Run downstream QA checks for semantic accuracy.
  • Store versioned output and audit metadata.

Error handling

Use the error-handling guidance below when requests fail.

  • Retry only transient transport failures.
  • Treat 4xx responses as request or input data issues, and then fix the input.
  • Capture request IDs and timestamps for support investigations.