magento
Overview of the Adobe Commerce and Magento Open Source REST API documentation.
16 channels
across 2 AsyncAPI specs
· Provider profile
Channels
-
Fired after a product is created or updated in the catalog. Used to synchronize product data with external PIM systems, search indexes, or marketplace integrations.Adobe Commerce Webhooks
-
Fired after a product is added to a customer's shopping cart. Used for real-time cart analytics, personalization, or fraud detection integrations.Adobe Commerce Webhooks
-
Fired after a customer account is deleted. Used to propagate account deletion to external CRM or marketing systems and honor data removal requests.Adobe Commerce Webhooks
-
Fired after a customer account is created or updated. Used to synchronize customer profile data with external CRM, marketing automation, or loyalty systems.Adobe Commerce Webhooks
-
Fired after an order invoice is marked as paid and payment has been captured. Used to trigger downstream accounting or revenue recognition workflows.Adobe Commerce Webhooks
-
Fired after a customer places an order. Contains the full order object including line items, billing and shipping addresses, and payment method. Used to notify downstream order management systems or EAdobe Commerce Webhooks
-
Fired after any order save operation, including status changes, comment additions, and shipment or invoice creation. Useful for monitoring order lifecycle changes and propagating status updates to extAdobe Commerce Webhooks
-
Fired after a shipment record is created or updated for an order. Used to relay tracking information and shipment status to external logistics platforms or customer notification systems.Adobe Commerce Webhooks
-
Emitted after a product is permanently deleted from the catalog. Use this to remove the product from external search indexes, PIM systems, or marketplace listings.Adobe Commerce Eventing
-
Emitted after a product record is saved in the catalog. Covers new product creation and updates to existing products. Use this to propagate catalog changes to external PIM, search, or marketplace systAdobe Commerce Eventing
-
Emitted after the checkout process completes and an order has been submitted. This event fires after the order is fully placed including payment authorization. Use for post-checkout analytics and campAdobe Commerce Eventing
-
Emitted when a new customer successfully registers an account in the storefront. Published to Adobe I/O Events for downstream CRM, marketing automation, or loyalty program integrations.Adobe Commerce Eventing
-
Emitted after a customer account is created or updated. Covers both admin-initiated profile changes and customer self-service updates. Use this to synchronize customer data with external CRM systems.Adobe Commerce Eventing
-
Emitted after a credit memo (refund) is created for an order. Use this event to trigger refund processing in accounting systems, loyalty point deductions, or customer service platforms.Adobe Commerce Eventing
-
Emitted after a new sales order is successfully placed. Published to Adobe I/O Events and routed to all subscribed App Builder applications. Use this event to trigger order processing workflows, notifAdobe Commerce Eventing
-
Emitted after any committed save of an order record. Covers status changes, invoice creation, shipment creation, and admin edits. Use this event to maintain real-time order status synchronization in eAdobe Commerce Eventing