canonical: https://jentic.com/apis/adyen.com/adyen-notification-configuration # Adyen Notification Configuration API The Adyen Notification Configuration API is the classic-platform interface for subscribing to and managing webhook notifications about events on an Adyen marketplace or platform integration, including verification check completions, payout events, and dispute updates. The six endpoints let an integration create, list, retrieve, update, and delete notification subscriptions, plus send a synthetic test event to verify a configured endpoint URL responds correctly. It targets Adyen's classic platforms model; new integrations should use Balance Platform notifications instead. ## For AI agents Subscribe to and manage Adyen classic-platform webhook notifications for verification, payout, and platform events, with end-to-end test delivery. ## Scope Does not process payments, move funds, or manage account holders - use only for subscribing to and managing classic-platform webhook notifications. ## Capabilities - Subscribe a webhook URL to platform events via POST /createNotificationConfiguration with the events array and target URL - Retrieve all notification subscriptions for a platform account via POST /getNotificationConfigurationList - Update an existing subscription's URL, events, or active state via POST /updateNotificationConfiguration - Send a synthetic test notification to verify endpoint connectivity via POST /testNotificationConfiguration - Remove obsolete subscriptions in bulk via POST /deleteNotificationConfigurations - Inspect a single subscription's configured event types and target URL via POST /getNotificationConfiguration ## Use cases ### Marketplace Onboarding Event Webhooks Marketplaces using Adyen's classic platforms model need to know when a sub-merchant's KYC verification completes, when a payout settles, or when a balance moves. POST /createNotificationConfiguration registers a webhook URL with a list of event types (ACCOUNT_HOLDER_VERIFICATION, ACCOUNT_HOLDER_PAYOUT, etc.). Adyen then POSTs JSON event payloads to that URL whenever a matching event fires. The configuration takes effect immediately and supports HMAC signing for authenticity. Example prompt: Call POST /createNotificationConfiguration with notificationConfigurationDetails.notifyURL, eventConfigs containing eventType=ACCOUNT_HOLDER_VERIFICATION, and active=true ### Webhook Endpoint Connectivity Test Before going live, integrators must confirm their webhook receiver is reachable, returns 200 OK, and validates HMAC signatures correctly. POST /testNotificationConfiguration accepts a notificationId and triggers Adyen to send a synthetic event of each subscribed type to the configured URL. The response includes the HTTP status code Adyen received from the endpoint, making it suitable for CI smoke tests after deployment. Example prompt: Call POST /testNotificationConfiguration with notificationId and assert the returned response status is 200 for each event in the test ### Subscription Lifecycle Management As a platform's event needs change, subscriptions must be updated or removed. POST /updateNotificationConfiguration changes the target URL, event list, or active flag in place. POST /deleteNotificationConfigurations accepts a list of IDs to remove in one call, which is useful when migrating from the classic platforms model to Balance Platform webhooks. Example prompt: Call POST /updateNotificationConfiguration to change the notifyURL of an existing notificationId from the staging host to production ### AI Agent Webhook Provisioning via Jentic An onboarding agent that needs to wire up Adyen events for a new sub-merchant searches Jentic for 'subscribe to Adyen platform notifications', loads the schema for createNotificationConfiguration, and executes with the desired URL and event list. Jentic injects the X-API-Key header from the encrypted vault so the agent never handles the raw secret, and returns the new notificationId for downstream use. Example prompt: Search Jentic for 'create Adyen notification subscription', load the createNotificationConfiguration schema, then execute with notifyURL and eventConfigs for the new sub-merchant ## Key endpoints | Method | Path | Description | | --- | --- | --- | | POST | /createNotificationConfiguration | Subscribe a webhook URL to platform events | | POST | /getNotificationConfigurationList | List all notification subscriptions | | POST | /getNotificationConfiguration | Retrieve a single subscription by ID | | POST | /updateNotificationConfiguration | Update URL, events, or active flag | | POST | /testNotificationConfiguration | Send a synthetic test notification | | POST | /deleteNotificationConfigurations | Delete one or more subscriptions | ## Key resources - **Notification Configurations** — Subscribe webhooks to platform events, list and inspect existing subscriptions, update URLs and event lists, and remove obsolete subscriptions - **Test Notifications** — Trigger synthetic notification deliveries to verify endpoint connectivity and HMAC signature handling ## Why Jentic - **Setup:** Wiring the Notification Configuration API by hand means handling its X-API-Key or basic auth and targeting the classic CAL host to manage webhook subscriptions. Through Jentic you install once, import the Notification Configuration API from the API Directory, store the key once, and your agent calls it. - **Permission scoping:** This API takes the notification configuration in the request body rather than a resource id in the URL path, so you limit the agent to the operations it needs, such as listing or testing a notification configuration. Because you pick the operations, create, update, and delete stay out unless you include them. - **Credential handling:** Your Adyen X-API-Key and basic auth credentials are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context. - **Discovery method:** Agents search Jentic by intent such as 'subscribe to adyen platform webhooks', and Jentic returns the createNotificationConfiguration operation with its input schema so the agent calls the right endpoint without browsing the reference docs. ## Related APIs - **Balance Platform Configuration Notification** — Modern Balance Platform replacement for classic configuration webhooks - **Balance Platform Payment Notification** — Modern payment-event webhooks for Balance Platform integrations - **Adyen Account API** — Manage account holders and verification on the same classic platform - **Adyen Fund API** — Move funds between accounts on the classic platforms model ## FAQ ### What authentication does the Notification Configuration API use? The API accepts an API key in the X-API-Key header or HTTP Basic auth using Adyen web-service user credentials. Both schemes are declared in the spec as ApiKeyAuth and BasicAuth. Through Jentic, credentials are stored encrypted in the vault and only a scoped token is exposed to the agent at runtime, so raw API keys never enter the agent's context. ### Can I test a webhook endpoint before going live with the Notification Configuration API? Yes. POST /testNotificationConfiguration accepts a notificationId and asks Adyen to send a synthetic event of each configured type to the registered URL. The response reports the HTTP status Adyen received from your endpoint, which is the recommended way to confirm a deployment can validate HMAC signatures and respond with 200 OK. ### What event types can I subscribe to with this API? The classic-platforms event catalogue includes ACCOUNT_HOLDER_VERIFICATION, ACCOUNT_HOLDER_STATUS_CHANGE, ACCOUNT_HOLDER_PAYOUT, ACCOUNT_HOLDER_UPCOMING_DEADLINE, BENEFICIARY_SETUP, COMPENSATE_NEGATIVE_BALANCE, REPORT_AVAILABLE, and TRANSFER_FUNDS, among others. You attach event types to a subscription via the eventConfigs array on POST /createNotificationConfiguration. ### What are the rate limits for the Notification Configuration API? Adyen does not publish a hard quantitative rate limit for the classic Notification Configuration endpoints in the OpenAPI spec; the API is intended for low-volume administrative use rather than per-transaction calls. If you receive 429 responses, contact Adyen support to review usage. ### How do I subscribe to verification events with the Notification Configuration API through Jentic? Search Jentic for 'create Adyen notification subscription', load the createNotificationConfiguration schema, then execute with notifyURL set to your webhook receiver and eventConfigs containing eventType=ACCOUNT_HOLDER_VERIFICATION and active=true. Jentic handles X-API-Key injection from the encrypted vault. Get an account through Jentic One, the self-hosted execution layer. ### Should I use this API or the Balance Platform notifications for new integrations? Adyen recommends the Balance Platform Configuration Notification, Payment Notification, Report Notification, and Transfer Notification webhooks for new platform integrations. The Notification Configuration API targets the classic platforms model. If you are starting a new integration, use the Balance Platform notification surfaces instead. ### Can I limit what my agent is allowed to do with the Adyen Notification Configuration API? Yes. Jentic One is self-hosted, so you run it yourself and your own rules decide which of this API's operations the agent may call and which credentials it may use. Because every operation takes the notification configuration in the request body rather than a resource id in the URL path, you can allow read-only actions such as getNotificationConfigurationList, getNotificationConfiguration, or testNotificationConfiguration while keeping createNotificationConfiguration, updateNotificationConfiguration, and deleteNotificationConfigurations off unless you explicitly include them. Your Adyen API key or basic auth is injected only at execution time and never enters the agent's prompt.