Adyen Configuration API

Name: Adyen Configuration API API
Brand: Adyen Configuration API
Availability: InStock

✓ Official Vendor SpecPaymentsBilling SubscriptionsapiKey, basic56 EndpointsREST

For Agents

Manage account holders, balance accounts, payment instruments, sweeps, and transaction rules across an Adyen for Platforms balance platform.

Quickstart

Get started with Adyen Configuration API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"create adyen balance account"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with Adyen Configuration API API.

Create and update account holders, including capabilities and KYC association via POST /accountHolders and PATCH /accountHolders/{id}

Provision balance accounts with currencies, default sweeps, and association to an account holder

Issue and manage payment instruments — physical and virtual cards, bank accounts — under POST /paymentInstruments

Configure automated sweeps that move funds between balance accounts on schedule or trigger

GET STARTED

Start building with Adyen Configuration API API

Explore with Jentic

View OpenAPI Spec

The Adyen Configuration API is the core REST surface for Adyen for Platforms. It manages account holders, balance accounts, payment instruments, payment instrument groups, transaction rules, sweeps, network tokens, and grant accounts across a balance platform. The 56 endpoints cover creation, read, update, and lifecycle operations for every structural object Adyen for Platforms exposes — from posting a new accountHolder to retrieving the platform configuration to managing card-level transaction rules.

Use Cases

Patterns agents use Adyen Configuration API API for, with concrete tasks.

★ Onboarding a Platform User End to End

When a marketplace or fintech onboards a new seller, freelancer, or sub-merchant, the Configuration API creates the structural objects that represent them in Adyen for Platforms. POST /accountHolders creates the entity, POST /balanceAccounts provisions a balance, and POST /paymentInstruments issues a card or bank account. Each object is updatable as KYC and capabilities evolve.

Call POST /accountHolders with legalEntityId, then POST /balanceAccounts referencing that accountHolderId, then POST /paymentInstruments to issue a virtual card on the new balance account

Dynamic Transaction Rule Management

Compliance and risk teams need to apply rules at multiple levels — block international transactions on cards, cap monthly volume on a balance account, or enforce MCC restrictions on a group of instruments. The Configuration API exposes transaction rules at account holder, balance account, payment instrument, and instrument group scope, so an agent or admin tool can adjust rules at the right level on the fly.

Call POST /transactionRules with entityType=paymentInstrument, scope to a specific paymentInstrumentId, and a ruleRestrictions block that blocks transactions outside the EU

Treasury Sweeps Between Balance Accounts

Treasury teams use automated sweeps to consolidate funds, fund operating accounts, or enforce minimum balances. The Configuration API's sweep endpoints under /balanceAccounts/{balanceAccountId}/sweeps create, read, update, and delete sweep configurations. Combined with the Transfer webhooks, this gives a closed loop: configure the sweep, then react to its events.

Call POST /balanceAccounts/{balanceAccountId}/sweeps with type=push, schedule.type=daily, and counterparty referencing the consolidation balance account

Agent-Driven Platform Operations via Jentic

An ops or fintech-engineering agent can use Jentic to discover and call the right Configuration API operation across 56 endpoints without scraping the Adyen developer portal. The agent searches by intent, loads the operation schema, and executes the call with X-API-Key managed in the Jentic vault.

Use Jentic to search 'create adyen balance account' and execute POST /balanceAccounts with the accountHolderId and currency for a new platform user

Key Endpoints

56 endpoints — the adyen configuration api is the core rest surface for adyen for platforms.

METHOD

PATH

DESCRIPTION

POST

/accountHolders

Create an account holder

GET

/accountHolders/{id}

Retrieve an account holder by id

PATCH

/accountHolders/{id}

Update an account holder

POST

/balanceAccounts

Create a balance account

GET

/balanceAccounts/{balanceAccountId}/sweeps

List sweeps on a balance account

POST

/paymentInstruments

Issue a payment instrument (card or bank account)

POST

/transactionRules

Create a transaction rule

POST

/accountHolders

Create an account holder

GET

/accountHolders/{id}

Retrieve an account holder by id

PATCH

/accountHolders/{id}

Update an account holder

POST

/balanceAccounts

Create a balance account

GET

/balanceAccounts/{balanceAccountId}/sweeps

List sweeps on a balance account

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Adyen X-API-Key, basic auth, and clientKey credentials are stored encrypted in the Jentic vault. Agents calling the Configuration API — which can issue cards and move structural state — never hold the raw credentials in their prompt context.

Intent-based discovery

Agents search Jentic by intent (for example 'create adyen balance account' or 'issue virtual card adyen') and Jentic returns the right operation among 56 endpoints with its full input schema, so the agent does not have to scan the developer portal.

Time to first call

Direct Adyen for Platforms integration: 1-2 weeks for credential setup, request/response handling across the structural objects, and webhook wiring. Through Jentic: under a day for the equivalent operations — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

Adyen Configuration webhooks

Webhook events that fire on the same mutations this REST API performs

Pair with the Configuration webhooks to react asynchronously to changes this API drives

Complementary

Adyen Transfer webhooks

Receives transfer events triggered by sweeps configured here

Use Transfer webhooks alongside this API to monitor the funds movement that follows a sweep configuration

Alternative

Stripe

Stripe Connect and Issuing offer a comparable platform-management surface

Choose Stripe Connect/Issuing when the underlying processor is Stripe rather than Adyen for Platforms

FAQs

Specific to using Adyen Configuration API API through Jentic.

What authentication does the Adyen Configuration API use?

The API supports an apiKey scheme using the X-API-Key header, HTTP basic auth, and a clientKey query parameter for client-side flows. Through Jentic, the X-API-Key is stored in the encrypted vault so agents call any of the 56 endpoints without holding the raw credential.

Can I issue cards through the Adyen Configuration API?

Yes. POST /paymentInstruments with type=card creates a card under a balance account, and PATCH /paymentInstruments/{id} updates its status. Card-level transaction rules are managed via POST /transactionRules with entityType=paymentInstrument.

What are the rate limits for the Adyen Configuration API?

The OpenAPI spec does not declare programmatic rate limits. Adyen documents per-merchant-account throughput limits in their developer portal — coordinate large onboarding batches with your Adyen account manager and prefer paginated reads where available.

How do I create a balance account through Jentic?

Search Jentic for 'create adyen balance account', load the POST /balanceAccounts operation, and execute it with the accountHolderId and currency. Jentic returns the structured response including the new balanceAccountId for use in downstream calls.

Does this API send webhook notifications for balance account changes?

No — this is the REST surface for mutations. Webhook notifications for the same events are delivered by the BalancePlatformConfigurationNotification webhook spec, which fires balancePlatform.balanceAccount.created and similar events when a mutation here completes.

Can I list every balance account owned by an account holder?

Yes. GET /accountHolders/{id}/balanceAccounts returns the balance accounts belonging to the given account holder. Pair with /accountHolders/{id}/transactionRules to inspect rules attached at the account holder level.