Skip to main content

Create a balance webhook setting

post/balancePlatforms/{balancePlatformId}/webhooks/{webhookId}/settings

Configures the criteria for triggering balance webhooks.

Adyen sends balance webhooks to notify you of balance changes in your balance platform. They can be triggered when the balance reaches, exceeds, or drops below a specific value in a specific currency.

You can get notified about balance changes in your entire balance platform, in the balance accounts of a specific user, or a specific balance account. The hierarchy between the webhook settings are based on the following business logic:

  • Settings on a higher level apply to all lower level resources (balance platform > account holder > balance acocunt).

  • The most granular setting overrides higher level settings (balance account > account holder > balance platform).

Endpoint destination URL
https://balanceplatform-api-test.adyen.com/bcl/v2/balancePlatforms/{balancePlatformId}/webhooks/{webhookId}/settings
Click to copy
webhookIdstringRequired

The unique identifier of the balance webhook.

balancePlatformIdstringRequired

The unique identifier of the balance platform.

conditionsarray[object]

The array of conditions a balance change must meet for Adyen to send the webhook.

currencystringRequired

The three-character ISO currency code of the balance.

statusstringRequired

The status of the webhook setting. Possible values:

  • active: You receive a balance webhook if any of the conditions in this setting are met.
  • inactive: You do not receive a balance webhook even if the conditions in this settings are met.
targetobjectRequired

The type and ID of the resource about whose balance changes you want to be notified.

typestringRequired

The type of the webhook you are configuring. Set to balance.

After submitting a call, you receive a response message to inform you that your request was received and processed.

Depending on the HTTP status code of the response message, it is helpful to build some logic to handle any errors that a request or the system may return.

HTTP Responses

  • 200 - OK

    The request has succeeded.

  • 400 - Bad Request

    A problem reading or understanding the request.

  • 401 - Unauthorized

    Authentication required.

  • 403 - Forbidden

    Insufficient permissions to process the request.

  • 404 - Not Found

    The payment was not found

  • 422 - Unprocessable Entity

    A request validation error.

  • 500 - Internal Server Error

    The server could not process the request.