API archive entry · source-reported

Notification Configuration API

This API is used for the classic integration. If you are just starting your implementation, refer to our new integration guide instead. The Notification Configuration API provides endpoints for setting up and testing notifications that inform you of events on your platform, for example when a verification check or a payout has been completed. For more information, refer to our documentation. ## Authentication Your Adyen contact will provide your API credential and an API key. To connect to the API, add an `X-API-Key` header with the API key as the value, for example: ``` curl -H "Content-Type: application/json" \ -H "X-API-Key: YOUR_API_KEY" \ ... ``` Alternatively, you can use the username and password to connect to the API using basic authentication. For example: ``` curl -U "ws@MarketPlace.YOUR_PLATFORM_ACCOUNT":"YOUR_WS_PASSWORD" \ -H "Content-Type: application/json" \ ... ``` When going live, you need to generate new web service user credentials to access the live endpoints. ## Versioning The Notification Configuration API supports versioning using a version suffix in the endpoint URL. This suffix has the following format: "vXX", where XX is the version number. For example: ``

Provider / source website

Documentation & source

Use the provider’s reference for current endpoints, setup, limits and terms.

No separate documentation URL has been confirmed for this record.

Open provider / source ↗

Provider content retains its own terms. This listing does not grant reuse or training rights.

Where these facts came from

AltAPIs imported it from APIs.guru OpenAPI Directory. The source link and dates remain visible for independent inspection.

What is reported

  • Name, category, and short description
  • Authentication label
  • HTTPS and CORS labels
  • Provider/source URL

What is not established

  • Current uptime or availability
  • Pricing, quotas, and rate limits
  • Security, compliance, or licensing posture
  • SDK quality or endpoint completeness

Record checkpoints

  1. First observed: Sep 20, 2026
  2. Last directory-field change: Sep 20, 2026
  3. Current source observation: Sep 20, 2026

Submit a source-backed correction

Source reference

APIs.guru OpenAPI Directory

This page separates source-reported facts from questions that need live provider verification.