The building blocks of I/O Events integrations.
Last checked 2026-09-30
CX Enterprise atlas / Developer & Extensibility | Developer & extensibility
Adobe I/O Events
ProductGenerally available
Developer & ExtensibilityDeveloper & extensibility
Also known as Adobe IO Events
Adobe's event delivery service. Event providers in Adobe products (AEM, Experience Platform, Commerce, Cloud Manager, Admin Console, Marketo Engage, GenStudio, Firefly Services and others) or custom providers publish events, and applications receive the event types they registered for through a webhook, an I/O Runtime action, Amazon EventBridge or the pull-based Journaling API. Registrations are set up in Adobe Developer Console or through the API, CLI and SDK.
Integrates with 2
Built on 1
Integrated by 4
- Adobe Developer App Builder
- Adobe Developer Console: I/O Management API, Event registrations in projects
- Adobe Marketo Engage: Marketo Data Streams
- Adobe Commerce: Catalog events
Foundation for 1
Contains 9 parts, 52 entries
- Event providers# Capability
A source of events, such as an AEM environment, a Commerce instance or a custom application. Each provider publishes event types identified by an event code; some providers are open to all customers, others need an enterprise developer role or a product licence.
Last checked 2026-09-30
- Event registrations# Capability
Also known as Event subscriptions
A subscription, owned by a Developer Console project or workspace and its OAuth credential, to chosen event types from one or more providers, with one or more delivery methods. An organization can hold up to 2,500 registrations, and one client ID up to 30 by default.
Integrates with: Event registrations in projects
Last checked 2026-09-30
- Registration states# Capability
A webhook registration is Active, Unstable or Disabled depending on delivery success over rolling windows: at least 10 attempts with 80% failing mark it Unstable, and after a further 24 hours it becomes Disabled. Admins get an email on each change, and a Disabled registration must be re-enabled by hand.
Last checked 2026-09-30
- Event formats# Capability
Also known as CloudEvents format
Events are JSON objects, delivered either in the CloudEvents 1.0 envelope or the older Adobe I/O format. Each carries a unique event ID (also sent in the x-adobe-event-id header) and the recipient client ID.
Last checked 2026-09-30
- Delivery guarantees# Capability
At-least-once, durable delivery per registration. Order is not guaranteed and duplicates can occur, so consumers deduplicate on the event ID.
Last checked 2026-09-30
- Delivery methods# Collection
Also known as Subscription types
Ways to receive events: push to a webhook, a Runtime action or Amazon EventBridge, or pull through the journal. A registration can combine push delivery with the journal.
Last checked 2026-09-30
- Webhooks# Capability
Also known as I/O Events webhooks
Adobe sends each event as an HTTP POST to a public HTTPS endpoint. Events come from AWS and Azure without fixed IP addresses; a webhook must answer within 10 seconds.
Last checked 2026-09-30
- Webhook challenge validation# Capability
On registration, Adobe sends a GET request with a challenge parameter that the webhook must echo back; if it does not, Adobe posts a URL for manual (asynchronous) validation.
Last checked 2026-09-30
- Single and batch delivery# Capability
Each webhook registration uses one event per request, or batches of up to 100 events and 2 MB per request.
Last checked 2026-09-30
- Delivery retries# Capability
Also known as Retry policy
Deliveries that time out or get a 429 or a 5xx response (except 505) are retried for up to 24 hours, first after 1 minute and then with doubling waits capped at 15 minutes, with an x-adobe-retry-count header. Events still undelivered after that are dropped, but remain in the journal for 7 days.
Last checked 2026-09-30
- Runtime actions as webhooks# Capability
An Adobe I/O Runtime action in the same project serves as the webhook. Signature verification is built in, the timeout is 60 seconds, delivery headers are passed through to the action, and debug tracing shows the action's activation ID and response.
Integrates with: I/O Runtime, Runtime namespaces in projects
Last checked 2026-09-30
- Automatic event registrations# Capability
Event registrations declared in an App Builder app's configuration are created when the app is deployed with aio app deploy and removed on undeploy; a PREFERRED_PROVIDERS variable picks providers in CI/CD.
Last checked 2026-09-30
- Journaling# Capability
Also known as Event journal
A pull model in which every registration also writes to a journal that the application reads in batches at its own pace, from a chosen point in time. Events are kept for 7 days; suited to long-running processing and to networks that cannot expose a public webhook.
Integrates with: Journaling API
Last checked 2026-09-30
- Amazon EventBridge delivery# Integration
Routes a registration's events to a partner event source in a customer AWS account and region, in the EventBridge envelope with the event under detail. Registrations using it cannot use subscriber-defined filtering.
Last checked 2026-09-30
- Delivery security# Collection
Ways a consumer can confirm that a webhook request really comes from Adobe I/O Events.
Last checked 2026-09-30
- Digital signatures# Capability
Also known as Signature verification
Every webhook request carries digital signatures over the payload, made with Adobe-held key pairs whose public keys are fetched from a URL in the headers, plus the recipient client ID for checking the event was meant for this integration.
Last checked 2026-09-30
- Mutual TLS# Capability
Also known as mTLS
If the webhook server requires client certificates, Adobe I/O Events presents its certificate during the TLS handshake, with no extra project configuration; an alternative to checking signatures.
Last checked 2026-09-30
- HIPAA support# Capability
I/O Events is HIPAA compliant. Custom event producers flag events that carry protected health information with an x-event-phidata header and keep their own mapping of event IDs to patient data.
Last checked 2026-09-30
- Subscriber-defined filtering# Capability
Also known as SDF, Subscriber Defined Filtering
JSON filters attached to a registration and evaluated on Adobe's side before delivery, so only matching events reach the webhook or journal. Operators include equals, anything-but, prefix, suffix, numeric, exists, equals-ignore-case, $or and cidr; filters can be validated first. Documented since September 2025 and available only for CloudEvents registrations without EventBridge.
Last checked 2026-09-30
- Filters in Developer Console# Capability
An Event Filtering tab on a registration in Developer Console for writing a filter and testing it against sample events.
Last checked 2026-09-30
- Filters API# API / SDK
Endpoints for creating, listing, reading, updating, deleting and validating a registration's filters.
Last checked 2026-09-30
- Adobe event providers# Collection
The Adobe products that publish events through I/O Events, as listed under "Using Adobe I/O Events". Each is added to a Developer Console project with Add event.
Integrates with: Marketo Data Streams
Last checked 2026-09-30
- AEM Cloud Service Events# Integration
Also known as Cloud-native AEM Events
Built-in eventing for AEM as a Cloud Service environments, needing no code in AEM: author events for Sites (pages, content fragments and models) and Assets, with more event types added over time. Enabled per environment by giving the user admin rights on its product profile.
Integrates with: AEM Events, Asset events, Experience Manager as a Cloud Service
Last checked 2026-09-30
- AEM Events add-on module# Integration, deprecated
The legacy open-source package (aio-lib-java aem-io-events) installed on AEM 6.5 on-premise or Managed Services to publish page and asset events to I/O Events.
Replaced by AEM Cloud Service Events
Last checked 2026-09-30
- Cloud Manager events# Integration
Notifications of events from Cloud Manager CI/CD pipelines, for system administrators or API developers. They go to webhooks, I/O Runtime or the journal, which suits networks that cannot expose a webhook.
Integrates with: Cloud Manager
Last checked 2026-09-30
- Adobe Commerce event provider# Integration
Commerce application and back-office events published through the Adobe I/O Events for Commerce module and commonly consumed by App Builder extensions.
Integrates with: I/O Events for Commerce, Commerce
Last checked 2026-09-30
- Platform notifications# Integration
Also known as Experience Platform notifications, Experience Platform events
Experience Platform alert and status events, such as data ingestion, sources and destinations flow runs and other Observability Insights alert rules, delivered as I/O Events.
Integrates with: Observability Insights, Experience Platform
Last checked 2026-09-30
- Privacy Service events# Integration
Status events for Experience Platform Privacy Service jobs, so integrations learn when access or delete requests finish without polling the API.
Integrates with: Privacy Service
Last checked 2026-09-30
- Data hygiene events# Integration
Events for monitoring Experience Platform data hygiene (Advanced Data Lifecycle Management) requests.
Integrates with: Advanced Data Lifecycle Management
Last checked 2026-09-30
- Journey Optimizer alert events# Integration
Journey Optimizer system alerts (journey errors, profile discards, campaign lifecycle and deliverability issues), which can be subscribed to per sandbox as I/O Events notifications.
Integrates with: System alerts, Journey Optimizer
Last checked 2026-09-30
- Analytics Triggers events# Integration
Events fired by Experience Cloud Triggers when a visitor behaviour defined on Adobe Analytics data occurs, such as cart abandonment, delivered to a webhook for follow-up.
Integrates with: CX Enterprise Triggers, Analytics
Last checked 2026-09-30
- GenStudio Events# Integration
GenStudio for Performance Marketing events for approved experiences being created, having metadata updated or being deleted, in CloudEvents 1.0 format. Documented since August 2026.
Integrates with: GenStudio for Performance Marketing
Last checked 2026-09-30
- Admin Console Audit Logs events# Integration
A stream of Admin Console audit log entries (users, groups, product profiles, roles, contracts and other changes), released in March 2026. Only users with the Admin developer role can add it to a project; a changelog tracks format changes.
Integrates with: Admin Console Audit Logs event provider, Admin developer role
Last checked 2026-09-30
- OCSF mapping# Capability
Audit events follow the Open Cybersecurity Schema Framework (OCSF), with custom entities for Adobe objects such as product profiles, contracts and roles, so they load into security tools directly.
Last checked 2026-09-30
- Content Log events# Integration
A stream of end-user interactions with assets (such as create, update and delete) for compliance tracking and loading into SIEM tools like Splunk or Microsoft Sentinel, in CloudEvents format. Added in July 2025.
Integrates with: Content Logs
Last checked 2026-09-30
- Firefly Services job events# Integration
Also known as Imaging APIs events
Job lifecycle events (created, processing, succeeded, failed, with outputs or errors) from Firefly Services APIs, as a push alternative to polling status URLs.
Integrates with: Asynchronous jobs and webhooks
Last checked 2026-09-30
- Photoshop and Lightroom API events# Integration
Job events for Photoshop API and Lightroom API requests.
Integrates with: Photoshop API, Lightroom API
Last checked 2026-09-30
- InDesign APIs events# Integration
Job processing events for InDesign APIs, including asset downloads, rendering and uploads.
Integrates with: InDesign API
Last checked 2026-09-30
- Dynamic Graphics Render events# Integration
Render job lifecycle notifications for the Dynamic Graphics Render API, in CloudEvents 1.0 format.
Integrates with: Dynamic Graphics Render API
Last checked 2026-09-30
- Creative Cloud Asset Events# Integration
Create, update and delete events for Creative Cloud files, directories, libraries and cloud documents (Photoshop, Illustrator, XD). Creative Cloud is outside this map, so it is listed only as an integration.
Last checked 2026-09-30
- Custom I/O Events# Capability
Also known as Custom Events Providers
Lets customers and partners register their own event providers and event metadata, then publish events from App Builder apps or other code so Adobe and third-party systems can react to them like any Adobe event.
Integrates with: Events Publishing API, App Builder custom events
Last checked 2026-09-30
- Adobe I/O Events API# Collection
Also known as I/O Events API
REST APIs, described in an OpenAPI reference, for automating registrations, providers and event consumption. They require the I/O Management API in the calling project.
Integrates with: I/O Management API
Last checked 2026-09-30
- Journaling API# API / SDK
Reads a registration's journal in batches with a limit, moving forward with links to newer events or seeking to a point in time; events expire after 7 days.
Last checked 2026-09-30
- Registration API# API / SDK
Creates, lists, updates and deletes event registrations and reads their status.
Last checked 2026-09-30
- Provider API# API / SDK
Lists the event providers an organization is entitled to and manages custom providers and their event metadata (event codes and descriptions).
Last checked 2026-09-30
- Events Publishing API# API / SDK
The ingress endpoint where custom providers publish CloudEvents; throttled at 3,000 requests per 5 seconds per API key, returning 429 with Retry-After.
Last checked 2026-09-30
- Events developer tooling# Collection
SDK, CLI and App Builder support for building event-driven applications.
Integrates with: Events templates
Last checked 2026-09-30
- Adobe I/O Events SDK# API / SDK
Also known as aio-lib-events
Open-source JavaScript library for managing providers and event metadata, creating webhook or journal registrations, publishing events, reading the journal and verifying signatures.
Last checked 2026-09-30
- Events plugin for Adobe I/O CLI# API / SDK
Also known as aio event, aio-cli-plugin-events
CLI commands (aio event) for listing, creating and deleting registrations, providers and event metadata in the project selected with aio console.
Integrates with: I/O CLI, aio console commands
Last checked 2026-09-30
- Adobe I/O Events modules for Workfront Fusion# Integration
Workfront Fusion modules that start a scenario from I/O Events for Adobe services without their own Fusion connector.
Integrates with: Other Adobe modules
Last checked 2026-09-30
- Debug tracing# Capability
A Developer Console tab showing the last 100 delivery attempts of a registration with request, response and custom 6xx codes for failures with no HTTP response, filterable by status; traces are kept for 7 days.
Last checked 2026-09-30