Set up a webhook
Subscribe to receive webhook notifications about events related to your company account. You can add basic authentication to make sure the data is secure.
To make this request, your API credential must have the following roles:
- Management API—Webhooks read and write
Path parameters
Unique identifier of the company account.
Request body
Indicates if expired SSL certificates are accepted. Default value: false.
Indicates if self-signed SSL certificates are accepted. Default value: false.
Indicates if untrusted SSL certificates are accepted. Default value: false.
Indicates if the webhook configuration is active. The field must be true for us to send webhooks about events related an account.
Format or protocol for receiving webhooks. Possible values:
- soap
- http
- json
Your description for this webhook configuration.
Shows how merchant accounts are filtered when configuring the webhook.
Possible values:
- allAccounts : Includes all merchant accounts, and does not require specifying filterMerchantAccounts.
- includeAccounts : The webhook is configured for the merchant accounts listed in filterMerchantAccounts.
- excludeAccounts : The webhook is not configured for the merchant accounts listed in filterMerchantAccounts.
A list of merchant account names that are included or excluded from receiving the webhook. Inclusion or exclusion is based on the value defined for filterMerchantAccountType.
Required if filterMerchantAccountType is either:
- includeAccounts
- excludeAccounts
Not needed for filterMerchantAccountType: allAccounts.
Network type for Terminal API notification webhooks. Possible values:
- public
- local
Default Value: public.
Password to access the webhook URL.
Indicates if the SOAP action header needs to be populated. Default value: false.
Only applies if communicationFormat: soap.
SSL version to access the public webhook URL specified in the url field. Possible values:
- TLSv1.3
- TLSv1.2
- HTTP - Only allowed on Test environment.
If not specified, the webhook will use sslVersion: TLSv1.2.
The type of webhook that is being created. Possible values are:
- standard
- account-settings-notification
- banktransfer-notification
- boletobancario-notification
- directdebit-notification
- ach-notification-of-change-notification
- direct-debit-notice-of-change-notification
- pending-notification
- ideal-notification
- ideal-pending-notification
- report-notification
- rreq-notification
- terminal-settings
- terminal-boarding
Find out more about standard webhooks and other types of webhooks.
Public URL where webhooks will be sent, for example https://www.domain.com/webhook-endpoint.
Username to access the webhook URL.
Example request
{
"communicationFormat": "soap",
"sslVersion": "TLSv1.2",
"url": "http://www.adyen.com"
}Response
OK - the request has succeeded.
Indicates if expired SSL certificates are accepted. Default value: false.
Indicates if self-signed SSL certificates are accepted. Default value: false.
Indicates if untrusted SSL certificates are accepted. Default value: false.
Reference to the account the webook is set on.
Indicates if the webhook configuration is active. The field must be true for you to receive webhooks about events related an account.
The alias of our SSL certificate. When you receive a notification from us, the alias from the HMAC signature will match this alias.
Format or protocol for receiving webhooks. Possible values:
- soap
- http
- json
Your description for this webhook configuration.
Shows how merchant accounts are included in company-level webhooks. Possible values:
- includeAccounts
- excludeAccounts
- allAccounts: Includes all merchant accounts, and does not require specifying filterMerchantAccounts.
A list of merchant account names that are included or excluded from receiving the webhook. Inclusion or exclusion is based on the value defined for filterMerchantAccountType.
Required if filterMerchantAccountType is either:
- includeAccounts
- excludeAccounts
Not needed for filterMerchantAccountType: allAccounts.
Indicates if the webhook configuration has errors that need troubleshooting. If the value is true, troubleshoot the configuration using the testing endpoint.
Indicates if the webhook is password protected.
The checksum of the HMAC key generated for this webhook. You can use this value to uniquely identify the HMAC key configured for this webhook.
Unique identifier for this webhook.
Network type for Terminal API details webhooks.
Indicates if the SOAP action header needs to be populated. Default value: false.
Only applies if communicationFormat: soap.
SSL version to access the public webhook URL specified in the url field. Possible values:
- TLSv1.3
- TLSv1.2
- HTTP - Only allowed on Test environment.
If not specified, the webhook will use sslVersion: TLSv1.2.
The type of webhook. Possible values are:
- standard
- account-settings-notification
- banktransfer-notification
- boletobancario-notification
- directdebit-notification
- ach-notification-of-change-notification
- direct-debit-notice-of-change-notification
- pending-notification
- ideal-notification
- ideal-pending-notification
- report-notification
- terminal-api-notification
- terminal-settings
- terminal-boarding
Find out more about standard webhooks and other types of webhooks.
Public URL where webhooks will be sent, for example https://www.domain.com/webhook-endpoint.
Username to access the webhook URL.
Example response
{
"communicationFormat": "soap",
"sslVersion": "TLSv1.2",
"url": "http://www.adyen.com"
}