Adobe Creative Suite · Arazzo Workflow

Adobe PDF Services Auto-tag PDF for Accessibility

Version 1.0.0

Upload a PDF, auto-tag it for accessibility, poll the job, and get the tagged output download URI.

1 workflow 3 source APIs 1 provider
View Spec View on GitHub CreativeDesignGraphicsPhotographyVideoArazzoWorkflows

Provider

adobe-creative-suite

Workflows

autotag-pdf
Upload a PDF, auto-tag it for accessibility, and resolve the tagged download URI.
Registers a source PDF asset, submits an auto-tag operation, polls the job to a terminal state, and returns the download URI of the accessibility-tagged PDF on success.
5 steps inputs: generateReport, shiftHeadings outputs: errors, jobID, outputDownloadUri, sourceAssetID
1
createUpload
Request an upload asset for the source PDF to auto-tag.
2
submitAutoTag
Submit an auto-tag operation against the uploaded PDF asset. The API returns a job id for polling.
3
pollOperation
Poll the auto-tag operation status, repeating while it is in progress and branching once it is done or failed.
4
getOutput
Retrieve the tagged PDF asset metadata and a fresh temporary download URI for the output file.
5
reportFailure
Surface the error details from the failed auto-tag operation.

Source API Descriptions

Arazzo Workflow Specification

Raw ↑
arazzo: 1.0.1
info:
  title: Adobe PDF Services Auto-tag PDF for Accessibility
  summary: Upload a PDF, auto-tag it for accessibility, poll the job, and get the tagged output download URI.
  description: >-
    Automatically adds accessibility tags to a PDF to make it compliant with
    PDF/UA and WCAG standards, using the Adobe PDF Services asynchronous job
    model. The workflow registers the source PDF by requesting an upload asset,
    submits an auto-tag operation, polls the operation status until it is done
    or failed, and resolves a temporary download URI for the tagged output.
    Every step spells out its request inline so the flow can be read and
    executed without opening the underlying OpenAPI description.
  version: 1.0.0
sourceDescriptions:
- name: accessibilityApi
  url: ../openapi/adobe-creative-suite-accessibility-api-openapi.yml
  type: openapi
- name: assetsApi
  url: ../openapi/adobe-creative-suite-assets-api-openapi.yml
  type: openapi
- name: operationsApi
  url: ../openapi/adobe-creative-suite-operations-api-openapi.yml
  type: openapi
workflows:
- workflowId: autotag-pdf
  summary: Upload a PDF, auto-tag it for accessibility, and resolve the tagged download URI.
  description: >-
    Registers a source PDF asset, submits an auto-tag operation, polls the job to
    a terminal state, and returns the download URI of the accessibility-tagged
    PDF on success.
  inputs:
    type: object
    properties:
      generateReport:
        type: boolean
        description: Whether to generate an accessibility report alongside the tagged PDF.
      shiftHeadings:
        type: boolean
        description: Whether to shift heading levels for better document structure.
  steps:
  - stepId: createUpload
    description: Request an upload asset for the source PDF to auto-tag.
    operationId: uploadAsset
    requestBody:
      contentType: application/json
      payload:
        mediaType: application/pdf
    successCriteria:
    - condition: $statusCode == 200
    outputs:
      assetID: $response.body#/assetID
      uploadUri: $response.body#/uploadUri
  - stepId: submitAutoTag
    description: >-
      Submit an auto-tag operation against the uploaded PDF asset. The API
      returns a job id for polling.
    operationId: autoTagPDF
    requestBody:
      contentType: application/json
      payload:
        assetID: $steps.createUpload.outputs.assetID
        generateReport: $inputs.generateReport
        shiftHeadings: $inputs.shiftHeadings
    successCriteria:
    - condition: $statusCode == 201
    outputs:
      jobID: $response.body#/jobID
  - stepId: pollOperation
    description: >-
      Poll the auto-tag operation status, repeating while it is in progress and
      branching once it is done or failed.
    operationId: getOperationStatus
    parameters:
    - name: jobId
      in: path
      value: $steps.submitAutoTag.outputs.jobID
    successCriteria:
    - condition: $statusCode == 200
    outputs:
      status: $response.body#/status
      assetID: $response.body#/asset/assetID
    onSuccess:
    - name: operationDone
      type: goto
      stepId: getOutput
      criteria:
      - context: $response.body
        condition: $.status == "done"
        type: jsonpath
    - name: operationFailed
      type: goto
      stepId: reportFailure
      criteria:
      - context: $response.body
        condition: $.status == "failed"
        type: jsonpath
    - name: stillRunning
      type: retry
      stepId: pollOperation
      retryAfter: 5
      retryLimit: 30
      criteria:
      - context: $response.body
        condition: $.status == "in progress"
        type: jsonpath
  - stepId: getOutput
    description: >-
      Retrieve the tagged PDF asset metadata and a fresh temporary download URI
      for the output file.
    operationId: getAsset
    parameters:
    - name: assetID
      in: path
      value: $steps.pollOperation.outputs.assetID
    successCriteria:
    - condition: $statusCode == 200
    outputs:
      downloadUri: $response.body#/downloadUri
      size: $response.body#/size
    onSuccess:
    - name: done
      type: end
  - stepId: reportFailure
    description: Surface the error details from the failed auto-tag operation.
    operationId: getOperationStatus
    parameters:
    - name: jobId
      in: path
      value: $steps.submitAutoTag.outputs.jobID
    successCriteria:
    - condition: $statusCode == 200
    outputs:
      errors: $response.body#/errors
  outputs:
    sourceAssetID: $steps.createUpload.outputs.assetID
    jobID: $steps.submitAutoTag.outputs.jobID
    outputDownloadUri: $steps.getOutput.outputs.downloadUri
    errors: $steps.reportFailure.outputs.errors

Work with this as data

Every workflow here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for arazzo workflows

4 MCP tools reach this
  • find_arazzoBrowse and filter every workflow in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This workflow
curl "https://apis.io/api/v1/arazzo/adobe-creative-suite-pdf-autotag-accessibility-workflow"
All arazzo workflows
curl "https://apis.io/api/v1/arazzo?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.