Specification for the webhook payloads Adyen sends from the classic Adyen for Platforms (MarketPay) integration, covering account holders, accounts, fund management, and other platform-level events. Adyen makes HTTP POST requests to the merchant's configured notification endpoint with a JSON body that the receiver authenticates using HTTP Basic credentials. Subscriptions are created and managed via the separate Notification Configuration API, while this spec describes the payload contract receivers must parse.
0 endpointsConfigure and manage Adyen company and merchant accounts, stores, payment terminals, payment methods, users, API credentials, allowed origins, webhooks, and Android apps and certificates from a single REST surface. Version 1 of the Management API exposes 130 operations against /v1, covering company-level, merchant-level, and store-level configuration without requiring access to the Customer Area UI. New integrations should consider Management API v3, which is the actively evolving version.
130 endpointsConfigure and manage Adyen company and merchant accounts, stores, payment terminals, payment methods, users, API credentials, allowed origins, webhooks, and Android apps and certificates from a single REST surface. Version 3 is the actively evolving Management API with 134 operations against /v3, including additional create-and-upload patterns on Android apps and certificates compared to v1. Recommended for new integrations that need programmatic control over the Adyen platform.
# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
"jentic": {
"url": "https://api.jentic.com/mcp",
"auth": "oauth"
}
}
# Then ask your agent:
"find live events near a location"
# → Jentic returns the GET /events tool with parameter schema, agent executes.