---
title: "Test an existing notification configuration."
method: POST
path: "/testNotificationConfiguration"
---

# Test an existing notification configuration.

`POST /testNotificationConfiguration`

This endpoint is used to test an existing notification subscription configuration. For each event type specified, a test notification will be generated and sent to the URL configured in the subscription specified.

## Request body

- TestNotificationConfigurationRequest
  - `eventTypes` string[] — The event types to test. If left blank, then all of the configured event types will be tested. >Permitted values: `ACCOUNT_HOLDER_CREATED`, `ACCOUNT_CREATED`, `ACCOUNT_UPDATED`, `ACCOUNT_HOLDER_UPDATED`, `ACCOUNT_HOLDER_STATUS_CHANGE`, `ACCOUNT_HOLDER_STORE_STATUS_CHANGE` `ACCOUNT_HOLDER_VERIFICATION`, `ACCOUNT_HOLDER_LIMIT_REACHED`, `ACCOUNT_HOLDER_PAYOUT`, `PAYMENT_FAILURE`, `SCHEDULED_REFUNDS`, `REPORT_AVAILABLE`, `TRANSFER_FUNDS`, `BENEFICIARY_SETUP`, `COMPENSATE_NEGATIVE_BALANCE`.
  - `notificationId` integer, required — The ID of the notification subscription configuration to be tested.

## Response `200`

OK - the request has succeeded.

- TestNotificationConfigurationResponse
  - `errorMessages` string[] — Any error messages encountered.
  - `eventTypes` string[], required — The event types that were tested. >Permitted values: `ACCOUNT_HOLDER_CREATED`, `ACCOUNT_CREATED`, `ACCOUNT_UPDATED`, `ACCOUNT_HOLDER_UPDATED`, `ACCOUNT_HOLDER_STATUS_CHANGE`, `ACCOUNT_HOLDER_STORE_STATUS_CHANGE` `ACCOUNT_HOLDER_VERIFICATION`, `ACCOUNT_HOLDER_LIMIT_REACHED`, `ACCOUNT_HOLDER_PAYOUT`, `PAYMENT_FAILURE`, `SCHEDULED_REFUNDS`, `REPORT_AVAILABLE`, `TRANSFER_FUNDS`, `BENEFICIARY_SETUP`, `COMPENSATE_NEGATIVE_BALANCE`.
  - `exchangeMessages` ExchangeMessage[], required — The notification message and related response messages.
    - `messageCode` string
    - `messageDescription` string
  - `notificationId` integer, required — The ID of the notification subscription configuration.
  - `okMessages` string[], required — A list of messages describing the testing steps.
  - `pspReference` string, required — The reference of a request. Can be used to uniquely identify the request.
  - `resultCode` string — The result code.
  - `submittedAsync` boolean, required — Indicates whether the request is processed synchronously or asynchronously. Depending on the request's platform settings, the following scenarios may be applied: * **sync:** The processing of the request is immediately attempted; it may result in an error if the providing service is unavailable. * **async:** The request is queued and will be executed when the providing service is available in the order in which the requests are received. * **asyncOnError:** The processing of the request is immediately attempted, but if the providing service is unavailable, the request is scheduled in a queue.

## Changes

- **2020-03-04** (v1) `8521f7daecb4` — 9 breaking, 2 warning, 24 info
  - the request's body type/format changed from `object`/`` to ``/``
  - removed the enum value `ACCOUNT_FUNDS_BELOW_THRESHOLD` of the request property `eventTypes/items/`
  - removed the enum value `ACCOUNT_HOLDER_MIGRATED` of the request property `eventTypes/items/`
  - removed the enum value `FUNDS_MIGRATED` of the request property `eventTypes/items/`
  - …31 more

[Change history](https://skmtc.dev/adyen/apis/notificationconfigurationservice/changes/testNotificationConfiguration/post.md)

---

[API](https://skmtc.dev/adyen/apis/notificationconfigurationservice.md) · [All operations](https://skmtc.dev/adyen/apis/notificationconfigurationservice/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/adyen/notificationconfigurationservice/revisions/8521f7daecb4/schema)