---
title: "Auto-tag PDFs via API"
canonical_url: "https://www.nutrient.io/guides/dws-accessibility/developer-guides/auto-tag-pdfs/"
md_url: "https://www.nutrient.io/guides/dws-accessibility/developer-guides/auto-tag-pdfs.md"
last_updated: "2026-06-09T10:24:29.130Z"
description: "Send PDFs to DWS Accessibility API and receive tagged output ready for accessibility QA."
---

# Auto-tag PDFs via API

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

## Multipart upload request

```bash

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

```bash

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

```

## Recommended pipeline pattern

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.

---

## Related pages

- [Accessibility best practices](/guides/dws-accessibility/developer-guides/accessibility-best-practices.md)
- [DWS Accessibility API developer guides](/guides/dws-accessibility/developer-guides.md)
- [Introduction to PDF/UA and auto-tagging](/guides/dws-accessibility/developer-guides/introduction-to-pdfua-and-auto-tagging.md)