Composable Frontend 2.0 Learn more 

  • Integrations (Event Subscriptions/Notifications)/
    Observable Events

    Observable Events

    You can pass multiple observable keys to the observes field of the integration object, or you can create individual events. You can use an array when you handle multiple webhooks at the same URL.

    Entity/ResourceActionObservable KeyAvailability Level - Store/Organization
    AddressCreatedaddress.createdStore
    Updatedaddress.updatedStore
    Deletedaddress.deletedStore
    AccountCreatedaccount.createdStore
    Updatedaccount.updatedStore
    Deletedaccount.deletedStore
    Account MemberCreatedaccount-member.createdStore
    Updatedaccount-member.updatedStore
    Deletedaccount-member.deletedStore
    Account MembershipCreatedaccount-membership.createdStore
    Updatedaccount-membership.updatedStore
    Deletedaccount-membership.deletedStore
    CartsUpdatedcart.updatedStore
    Deletedcart.deletedStore
    CurrencyCreatedcurrency.createdStore
    Updatedcurrency.updatedStore
    Deletedcurrency.deletedStore
    CustomerCreatedcustomer.createdStore
    Updatedcustomer.updatedStore
    Deletedcustomer.deletedStore
    FileCreatedfile.createdStore
    Deletedfile.deletedStore
    Integration (events)Createdintegration.createdStore, Organization
    Updatedintegration.updatedStore, Organization
    Deletedintegration.deletedStore, Organization
    One-Time Password Token RequestCreatedone-time-password-token-request.createdStore
    Order Events
    /checkoutCreatedorder.createdStore
    /orders/:id/paymentsUpdatedorder.updated/order.paid. The event order.paid is triggered when the payment status is paid. The event order.updated is triggered when the order is captured, completed, refunded, anonymized, or updated.Store
    /orders/:idFulfilled/Canceledorder.fulfilled/order.cancelledStore
    /orders/:id/paymentsAuthorizedorder.authorizedStore
    /orders/:id/transactions/:id/capturePaid/Capturedorder.paid/ order.updated. The event order.paid is triggered when the order status is completed and captured, and the payment status is paid. The event order.updated is triggered when the order is captured, completed, refunded, anonymized, or updated.Store
    /orders/:id/transactions/:id/refundRefundedorder.refundedStore
    Payment GatewayUpdatedpayment-gateway.updatedStore
    Catalog
    Catalog releasesCreatedcatalog-release.createdStore, Organization
    Updatedcatalog-release.updatedStore, Organization
    Deletedcatalog-release.deletedStore, Organization
    Catalog rulesCreatedcatalog-rule.createdStore
    Updatedcatalog-rule.updatedStore
    Deletedcatalog-rule.deletedStore
    SettingsCreatedsettings.createdStore
    Updatedsettings.updatedStore
    Stock TransactionCreatedstock-transaction.createdStore
    TransactionCreatedtransaction.createdStore
    Updatedtransaction.updatedStore
    User Authentication InfoCreateduser-authentication-info.createdStore
    Updateduser-authentication-info.updatedStore
    Deleteduser-authentication-info.deletedStore

    Store-level events contain store_id and org_id whereas, organization-level events contain only org_id.

    Previous
    Integration Examples