Adyen Notification Configuration API
Browse all Adyen APIs✓ Official Vendor SpecPaymentsPayment ProcessingapiKey, basic6 EndpointsREST
For Agents
Subscribe to and manage Adyen classic-platform webhook notifications for verification, payout, and platform events, with end-to-end test delivery.
Use for: Subscribe my platform to verification check notifications from Adyen, List all webhook notification configurations for my classic platform account, Send a test notification to verify my webhook endpoint is responding, Update the URL of an existing Adyen notification subscription
Not supported: Does not process payments, move funds, or manage account holders — use only for subscribing to and managing classic-platform webhook notifications.
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.
Install Jentic One Beta
Connect the Notification Configuration API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Notification Configuration API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with Notification Configuration API.
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
Patterns agents use Notification Configuration API for, with concrete tasks.
★ 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.
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.
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.
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.
Search Jentic for 'create Adyen notification subscription', load the createNotificationConfiguration schema, then execute with notifyURL and eventConfigs for the new sub-merchant
Key Endpoints
6 endpoints — 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.
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
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
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
Adyen API keys and basic-auth credentials are stored encrypted in the Jentic vault. Agents receive scoped access tokens at execution time — the raw X-API-Key header value never enters the agent's context.
Intent-based discovery
Agents search by intent (e.g., 'subscribe to Adyen platform webhooks') and Jentic returns the matching createNotificationConfiguration operation with its full input schema, so the agent can call the right endpoint without crawling Adyen's classic platforms documentation.
Time to first call
Direct Adyen integration: 1-2 days for credential setup, classic-platforms model orientation, HMAC signature verification, and webhook receiver wiring. Through Jentic: under 30 minutes — search, load, execute.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Notification Configuration API through Jentic.
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 at https://app.jentic.com/sign-up.
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.
GET STARTED