generated: '2026-08-13'
method: searched
source: >-
  https://developer.adobe.com/document-services/docs/overview/releasenotes/ ,
  https://developer.adobe.com/developer-console/docs/guides/authentication/ ,
  https://status.adobe.com/ , https://experienceleague.adobe.com/ ,
  plus deprecated operations derived from openapi/
versioning:
  house_standard: false
  note: >-
    Adobe publishes a real, written versioning and support policy for PDF Services, and
    per-product schemes everywhere else. There is no estate-wide version policy.
  policies:
  - product: PDF Services SDK
    scheme: semver
    docs: https://developer.adobe.com/document-services/docs/overview/releasenotes/
    policy_verbatim: >-
      "Major Releases (1.x.x): Major releases introduce backward-incompatible changes to
      the APIs and interfaces and start the EOL clock for all previous releases. Minor
      Releases (x.1.x): Minor releases typically appear quarterly. Changes are backward
      compatible to the last major release... some interfaces may be deprecated;
      deprecated interfaces will be removed in a next major release. Patch Releases
      (x.x.1): Patch releases only deliver critical security or bug fixes as needed."
  - product: PDF Services Public API
    scheme: assetId-per-operation
    docs: https://developer.adobe.com/document-services/docs/overview/releasenotes/
    policy_verbatim: >-
      "each operation has a unique assetId which is passed in Form Parameters. Generally,
      APIs will be enhanced while keeping them backward compatible. If its functionality
      can't be enhanced without breaking changes, then its new version will be released
      with its own unique assetId."
  - {product: Adobe Analytics, scheme: uri-path, current: '2.0'}
  - {product: Firefly Services, scheme: uri-path, current: 'v3/v4 by model generation'}
  - {product: Workfront, scheme: uri-path, current: 'v19.0'}
  - {product: Adobe Commerce, scheme: 'uri-path + release line', current: '2.4.6'}
  - {product: Adobe Experience Platform, scheme: per-service uri-path, current: 'varies by service'}
deprecation:
  policy_url: https://developer.adobe.com/document-services/docs/overview/releasenotes/
  sunset_header: false
  deprecation_header: false
  note: >-
    Adobe does NOT implement RFC 8594 Sunset or the Deprecation header on any harvested
    contract. Deprecation is communicated in prose, in release notes, and via the
    OpenAPI `deprecated: true` flag. Retirement dates are announced on Experience League
    and the developer blog with months of notice — the JWT/Service Account credential
    retirement (2025-06-30) is the reference example, announced roughly two years ahead.
  announced_retirements:
  - item: JWT (Service Account) credential
    retired: '2025-06-30'
    replacement: OAuth Server-to-Server credential
    docs: https://developer.adobe.com/developer-console/docs/guides/authentication/
  - item: Workfront Unified Approvals API
    status: deprecated
    evidence: 'openapi/adobe-suite-workfront-unified-approvals-openapi.json — info.title is "Unified Approvals API (Deprecated)"'
  - item: Adobe Express add-on APIs queueAsyncEdit, PageNode.artboards, PageNode.allDescendants, PageNode.allTextContent, PageNode.cloneInPlace
    status: removed
    removed: '2026-08-03'
    docs: https://developer.adobe.com/express/add-ons/docs/guides/getting-started/changelog/
    note: 'Adobe: "removed from the SDK—local builds that still reference them will fail."'
  - item: Adobe Express add-ons that break in dark mode
    status: rejection-from
    effective: '2026-08-31'
    docs: https://developer.adobe.com/express/add-ons/docs/guides/getting-started/changelog/
deprecated_operations:
  count: 0
  note: >-
    No operation in the 70 harvested specs carries `deprecated: true`. Adobe retires
    whole documents (e.g. the Unified Approvals API, the AEP messagingold and
    campaigns-retrieve-old specs) rather than flagging individual operations, which means
    an agent reading a single Adobe contract cannot tell what is on its way out.
  superseded_specs_observed:
  - AdobeDocs/journey-optimizer-apis static/messagingold.yaml (superseded by messaging.yaml)
  - AdobeDocs/journey-optimizer-apis static/campaigns-retrieve-old.yaml (superseded by campaigns-retrieve.yaml)
  - AdobeDocs/pdfservices-api-documentation legacy-documentation/ release notes
sla:
  url: null
  uptime_target: null
  note: >-
    Adobe publishes no public API uptime SLA. SLAs are contractual and attached to
    Experience Cloud / Creative Cloud for enterprise agreements.
status_page: https://status.adobe.com/
status_api:
  spec: openapi/adobe-suite-status-openapi.yaml
  server: https://status.adobe.io/
  operations: 11
  auth: 'apiKey (api_key query param, documented public value "StatusAdobeIOClient") + bearer'
  note: >-
    Adobe is one of the small number of providers that publishes its status page as a
    machine-readable OpenAPI, not just an HTML page. That contract is harvested in this repo.
release_notes:
- {product: PDF Services, url: 'https://developer.adobe.com/document-services/docs/overview/releasenotes/'}
- {product: PDF Embed API, url: 'https://developer.adobe.com/document-services/docs/overview/pdf-embed-api/releasenotes/'}
- {product: Acrobat Sign, url: 'https://developer.adobe.com/sign/docs/'}
- {product: Adobe Express Add-ons, url: 'https://developer.adobe.com/express/add-ons/docs/guides/getting-started/changelog/'}
- {product: Adobe I/O CLI, url: 'https://github.com/AdobeDocs/adobeio-cli/blob/main/releasenotes.md'}
cross_links:
  changelog: changelog/adobe-suite-changelog.yml
  conventions: conventions/adobe-suite-conventions.yml