Webhook configuration reference
Webhooks are configured in a webhooks.xml
file. This file can be placed in the system <install_directory>/app/etc
directory or in the etc
directory of an enabled Adobe Commerce module.
Run the bin/magento webhooks:list
command to determine if the webhooks you create in this file register correctly. The webhook name will be displayed in the list of registered webhooks.
A maximal webhooks.xml
file has the following structure:
Copied to your clipboard|__ config|__ method|__ hooks|__ batch|__ hook|__ headers| |__ header|__ fields| |__ field|__ rules|__ rule
Configure hooks and Create conditional webhooks contain examples of fully-defined hooks.
config
attributes
The config
element must contain the following text:
Copied to your clipboard<config xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"xsi:noNamespaceSchemaLocation="urn:magento:module:Magento_AdobeCommerceWebhooks:etc/webhooks.xsd">...</config>
method
element
The method
element must define the webhook name
and type
. The combination of method name
and type
must be unique across the system.
Attribute | Type | Description | Is required |
---|---|---|---|
name | String | The webhook code name. The value must be in the form <type>.<webhook_name> , where type is either observer or plugin , and webhook_name matches a valid Commerce event name. Use the bin/magento webhooks:list:all command to display a list of possible webhooks. | true |
type | String | Specifies whether the webhook should be executed before or after the original action. | true |
hooks
element
The hooks
element is required. It does not contain any attributes, but it must contain one or more batch
elements.
batch
element
The batch
element sets the order in which multiple webhooks are executed. All hooks within a batch are sent in parallel. Therefore, as you add hooks to a batch, keep in mind what task each hook will perform. For example, since the hooks are executed in parallel, you should not place a hook that relies on a response from another hook in the same batch.
Attribute | Type | Description | Is required | Default |
---|---|---|---|---|
name | String | A unique name for the batch. This value must contain English alphanumeric characters and underscores (_) only. | true | Not applicable |
order | Int | Sort order for batch execution. | false | Not applicable |
hook
element
The hook
element defines the HTTP request to the remote server.
Attribute | Type | Description | Is required | Default |
---|---|---|---|---|
name | String | A hook name that is unique within a batch. | true | Not applicable |
url | String | The HTTP endpoint to send the request for processing. | true | Not applicable |
method | String | The HTTP method, such as POST or PUT, that invokes the hook. | false | POST |
priority | Int | The priority of the merging hook results in the batch. | false | 0 |
required | Boolean | Specifies whether hook execution is required or optional. When set to false (optional), if the hook fails to execute, the failure is logged and subsequent hooks continue to be processed. When true , a failure terminates the process. | false | true |
timeout | Int | A hard timeout limit (milliseconds) for the request. Requests exceeding this timeout are aborted and logged. The default value of 0 indicates there is no timeout limit. | false | 0 |
softTimeout | Int | A soft timeout limit (milliseconds) for the request. Requests exceeding this timeout are logged for debugging purposes. | false | Not applicable |
fallbackErrorMessage | Int | The error message to return when the hook fails. | false | Not applicable |
remove | Boolean | Indicates whether to skip a removed hook during the batch execution. | false | false |
ttl | Int | The cache time-to-live (in seconds) for requests with the same URL, body, and headers. If this attribute is not specified, or if the value set to 0 , the response is not cached. | false | 0 |
sslVerification | Boolean | Specifies whether SSL certificate verification would be performed during request. Enabled by default. This option should only be used for development purposes. | false | true |
sslCertificatePath | String | Specifies the path to a custom SSL certificate file to use for SSL verification. This option will be ignored if sslVerification is set to false. | false | Not applicable |
headers | Array | A set of HTTP headers to send with the request. | false | [] |
fields | Array | A set of fields to include in the hook payload. If not set, the entire payload will be sent. | false | [] |
headers
and header
elements
A headers
element is optional and can contain one or more header
elements. Each header
definition creates an HTTP header to be sent in the remote server request.
Attribute | Type | Description | Is required | Default |
---|---|---|---|---|
name | String | The header name, in the same form as it will be sent. For example, Authorization . Specify the value, such as Bearer: <token> in the body of the <header> element. | false | Not applicable |
resolver | String | The resolver class that appends headers dynamically. | false | Not applicable |
remove | Boolean | Set to true to remove the header from the request. | false | false |
fields
and field
elements
A fields
element is optional and can contain one or more field
elements. The fields
element provides the ability to limit the payload of a webhook to only those fields defined in the individual field
definitions. Define the hook body shows a fully-constructed hook.
Attribute | Type | Description | Is required | Default |
---|---|---|---|---|
name | String | The path to the field to include in the transmitted webhook, such as product.sku . | true | Not applicable |
source | String | The path to the value in the default webhook. If not set, the value of name is used. | false | Not applicable |
converter | String | A class that transforms the value of a field, such as from integer to string. | false | Not applicable |
remove | Boolean | Set to true to remove the field from the payload. | false | false |
rules
and rule
elements
A rules
element is optional and can contain one or more rule
elements. Each rule
element defines a conditional webhook, which configures the conditions that cause the webhook to be triggered when all conditions evaluate to true
. Create conditional webhooks provides example rules and fully describes the possible operator values.
Attribute | Type | Description | Is required | Default |
---|---|---|---|---|
field | String | The event field to be evaluated. For nested fields, use the dot-separated format, such as data.order.product.id . | true | Not applicable |
operator | String | A string that defines which comparison operator to use. Examples include equal , notEqual , and regex . | true | Not applicable |
value | String | The value to be compared. | true | Not applicable |
remove | Boolean | Indicates whether the rule is active. The default value of true indicates the rule is active. | false | false |