Properties
| Name | Type | Description |
|---|---|---|
| errorMessages | array | Any error messages encountered. |
| eventTypes | array | 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_STA |
| exchangeMessages | array | The notification message and related response messages. |
| invalidFields | array | Contains field validation errors that would prevent requests from being processed. |
| notificationId | integer | The ID of the notification subscription configuration. |
| okMessages | array | 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. |
JSON Schema
{
"$schema": "https://json-schema.org/draft/2020-12/schema",
"$id": "#/components/schemas/TestNotificationConfigurationResponse",
"title": "TestNotificationConfigurationResponse",
"properties": {
"errorMessages": {
"description": "Any error messages encountered.",
"items": {
"type": "string"
},
"type": "array"
},
"eventTypes": {
"description": "The event types that were tested.\n>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`.",
"items": {
"enum": [
"ACCOUNT_CLOSED",
"ACCOUNT_CREATED",
"ACCOUNT_FUNDS_BELOW_THRESHOLD",
"ACCOUNT_HOLDER_CREATED",
"ACCOUNT_HOLDER_LIMIT_REACHED",
"ACCOUNT_HOLDER_MIGRATED",
"ACCOUNT_HOLDER_PAYOUT",
"ACCOUNT_HOLDER_STATUS_CHANGE",
"ACCOUNT_HOLDER_STORE_STATUS_CHANGE",
"ACCOUNT_HOLDER_UPCOMING_DEADLINE",
"ACCOUNT_HOLDER_UPDATED",
"ACCOUNT_HOLDER_VERIFICATION",
"ACCOUNT_UPDATED",
"BENEFICIARY_SETUP",
"COMPENSATE_NEGATIVE_BALANCE",
"DIRECT_DEBIT_INITIATED",
"FUNDS_MIGRATED",
"PAYMENT_FAILURE",
"PENDING_CREDIT",
"REFUND_FUNDS_TRANSFER",
"REPORT_AVAILABLE",
"SCHEDULED_REFUNDS",
"SCORE_SIGNAL_TRIGGERED",
"TRANSFER_FUNDS",
"TRANSFER_NOT_PAIDOUT_TRANSFERS"
],
"type": "string"
},
"type": "array"
},
"exchangeMessages": {
"description": "The notification message and related response messages.",
"items": {
"$ref": "#/components/schemas/ExchangeMessage"
},
"type": "array"
},
"invalidFields": {
"x-addedInVersion": "5",
"description": "Contains field validation errors that would prevent requests from being processed.",
"items": {
"$ref": "#/components/schemas/ErrorFieldType"
},
"type": "array"
},
"notificationId": {
"description": "The ID of the notification subscription configuration.",
"format": "int64",
"type": "integer"
},
"okMessages": {
"description": "A list of messages describing the testing steps.",
"items": {
"type": "string"
},
"type": "array"
},
"pspReference": {
"description": "The reference of a request. Can be used to uniquely identify the request.",
"type": "string"
},
"resultCode": {
"description": "The result code.",
"type": "string"
}
},
"required": [
"notificationId"
],
"type": "object"
}
Work with this as data
Every JSON Schema here is available over the APIs.io API and to AI agents over MCP.
MCP server
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
Tools for schemas
4 MCP tools reach this
find_json_schemasBrowse and filter every JSON Schema in the catalog.apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.resolveTurn a domain, URL or GitHub org into the provider it belongs to.find_cohortsEvery scored population of providers in the catalog.
Call it yourself
curl for this page
This JSON Schema
curl "https://apis.io/api/v1/json-schemas/adyen-testnotificationconfigurationresponse"
All schemas
curl "https://apis.io/api/v1/json-schemas?limit=25"
Discovery needs no key. Ratings and market analysis are Pro.
Get an API key
Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.
A second provider on the same verified email joins the account you already have.