generated: '2026-08-13'
method: searched
spec_type: Webhooks
source: >-
  https://developer.adobe.com/events/docs/guides/ ,
  https://github.com/AdobeDocs/adobeio-events ,
  https://developer.adobe.com/creative-cloud-libraries/docs/integrate/guides/configuring-events-webhooks/ ,
  https://developer.adobe.com/firefly-services/docs/photoshop/getting_started/webhooks/ ,
  openapi/adobe-suite-cloud-manager-events-openapi.yaml
asyncapi_published: false
asyncapi_note: >-
  Adobe publishes NO AsyncAPI document. A code search across the entire AdobeDocs GitHub
  organization and the adobe organization returned zero AsyncAPI files. The event surface
  below is real and substantial, but the only machine-readable expression of any of it is
  one OpenAPI 3.1.0 document that uses the `webhooks` root object for Cloud Manager.
  Nothing here is fabricated as AsyncAPI.
platform:
  name: Adobe I/O Events
  docs: https://developer.adobe.com/events/docs/guides/
  model: >-
    An application creates an event registration in the Adobe Developer Console naming a
    webhook URL and the event types it wants. Each event becomes an HTTP POST to that URL.
    Events originate from Event Providers; each provider publishes event types identified
    by an Event Code.
  delivery_modes:
  - mode: webhook
    docs: https://developer.adobe.com/events/docs/guides/
    note: Push. Requires a publicly reachable HTTPS endpoint and a challenge-response verification handshake.
  - mode: journaling
    docs: https://developer.adobe.com/events/docs/guides/api/journaling_api/
    note: >-
      Pull. Adobe retains an ordered journal of events the registration can page through —
      the durable alternative for consumers that cannot expose a public endpoint.
  - mode: runtime-action
    note: Events can be routed directly to an Adobe I/O Runtime (App Builder) action instead of an external URL.
  apis:
  - {name: Provider API, docs: 'https://developer.adobe.com/events/docs/guides/api/provider_api/'}
  - {name: Registration API, docs: 'https://developer.adobe.com/events/docs/guides/api/registration_api/'}
  - {name: Events Ingress API, docs: 'https://developer.adobe.com/events/docs/guides/api/eventsingress_api/'}
  - {name: Journaling API, docs: 'https://developer.adobe.com/events/docs/guides/api/journaling_api/'}
  sdk:
    package: "@adobe/aio-lib-events"
    version: 4.1.0
    published: '2026-05-13'
    url: https://www.npmjs.com/package/@adobe/aio-lib-events
  cli:
    command: aio event
    package: "@adobe/aio-cli"
machine_readable_events:
- spec: openapi/adobe-suite-cloud-manager-events-openapi.yaml
  format: OpenAPI 3.1.0 `webhooks` object
  title: Cloud Manager Event Definitions
  server: https://cloudmanager.adobe.io
  event_count: 5
  events:
  - {name: PipelineExecutionStartEvent, summary: Pipeline Execution Start Event}
  - {name: PipelineExecutionStepStartEvent, summary: Pipeline Execution Step Start Event}
  - {name: PipelineExecutionStepWaitingEvent, summary: Pipeline Execution Step Waiting Event}
  - {name: PipelineExecutionStepEndEvent, summary: Pipeline Execution Step End Event}
  - {name: PipelineExecutionEndEvent, summary: Pipeline Execution End Event}
  note: >-
    The only Adobe event surface with a published schema. Each event carries a
    requestBody schema under components.schemas, so an agent can validate payloads.
documented_event_surfaces:
- product: Adobe Cloud Manager
  events: 5
  machine_readable: true
  docs: https://developer.adobe.com/experience-cloud/cloud-manager/guides/getting-started/create-event-integration/
- product: Photoshop API / Firefly Services
  machine_readable: false
  docs: https://developer.adobe.com/firefly-services/docs/photoshop/getting_started/webhooks/
  note: >-
    Job-completion callbacks delivered through Adobe I/O Events — the push alternative to
    polling the submit-then-poll async model recorded in conventions/.
- product: Adobe Creative Cloud Libraries
  machine_readable: false
  docs: https://developer.adobe.com/creative-cloud-libraries/docs/integrate/guides/configuring-events-webhooks/
- product: Adobe Acrobat Sign
  machine_readable: false
  docs: https://developer.adobe.com/sign/docs/webhooks/
  note: Acrobat Sign ships its own webhook subsystem (agreement, megaSign, widget, library document events) separate from Adobe I/O Events.
- product: Adobe Acrobat Services
  machine_readable: false
  docs: https://blog.developer.adobe.com/introducing-webhook-support-in-acrobat-services-9d16f4e3e6c8
  note: Webhook support announced 2024-01-25 on the Adobe Developers blog.
- product: Adobe Experience Platform
  machine_readable: false
  docs: https://experienceleague.adobe.com/en/docs/experience-platform/observability/alerts/subscribe
  note: Alerts and observability notifications subscribe through Adobe I/O Events.
- product: Adobe Commerce
  machine_readable: false
  docs: https://developer.adobe.com/commerce/extensibility/events/
- product: Adobe Learning Manager
  machine_readable: false
  docs: https://experienceleague.adobe.com/en/docs/learning-manager/using/integration/webhooks/
gaps:
- No AsyncAPI document exists for any Adobe event surface.
- >-
  No published event-type catalog in machine-readable form outside Cloud Manager. Event
  Codes are discoverable only by creating a registration in the Developer Console, which
  makes the event surface effectively gated for an agent doing discovery.
- No published event payload schema registry for Acrobat Sign, Commerce, AEP or Firefly.