---
title: "Test an existing notification configuration."
method: POST
path: "/testNotificationConfiguration"
tags: ["General"]
---

# 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 — The reference of a request. Can be used to uniquely identify the request.
  - `resultCode` string — The result code.
  - `submittedAsync` boolean — Indicates whether the request is processed asynchronously. Depending on the request's platform settings, the following scenarios may be applied: * **true**: The request is queued and will be executed when the providing service is available in the order in which the requests are received. * **false**: The processing of the request is immediately attempted; it may result in an error if the providing service is unavailable.

## Other responses

- `400` — Bad Request - a problem reading or understanding the request.
- `401` — Unauthorized - authentication required.
- `403` — Forbidden - insufficient permissions to process the request.
- `422` — Unprocessable Entity - a request validation error.
- `500` — Internal Server Error - the server could not process the request.

## Changes

- **2021-08-07** (v1) `c8ceb47d7b76` — 1 info
  - api tag `General` added
- **2021-07-09** (v1) `4184946e3e8d` — 2 info
  - the endpoint scheme security `ApiKeyAuth` was added to the API
  - the endpoint scheme security `BasicAuth` was added to the API
- **2021-04-24** (v1) `64ced2e58234` — 1 warning, 1 info
  - added the new `TRANSFER_NOT_PAIDOUT_TRANSFERS` enum value to the `eventTypes/items/` response property for the response status `200`
  - added the new `TRANSFER_NOT_PAIDOUT_TRANSFERS` enum value to the request property `eventTypes/items/`
- **2021-04-10** (v1) `fa01a51bf28a` — 5 info
  - added the optional property `status` to the response with the `400` status
  - added the optional property `status` to the response with the `401` status
  - added the optional property `status` to the response with the `403` status
  - added the optional property `status` to the response with the `422` status
  - …1 more
- **2021-03-26** (v1) `988c95b5257a` — 5 info
  - added the non-success response with the status `400`
  - added the non-success response with the status `401`
  - added the non-success response with the status `403`
  - added the non-success response with the status `422`
  - …1 more

[Full 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/c8ceb47d7b76/schema)