Adyen Configuration API

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

✓ Official Vendor SpecPaymentsBilling SubscriptionsapiKey, basic56 EndpointsREST

Install Jentic One Beta

Connect the Adyen Configuration API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Adyen 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.

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 | sh

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 instance

Jentic 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 Adyen Configuration 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

GET STARTED

Start building with Adyen Configuration API

Explore with Jentic

View OpenAPI Document

For Agents

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

Use for: Create an account holder for a new platform user, Update an account holder's capabilities to enable card issuing, Provision a balance account with a default sweep, Issue a virtual card as a payment instrument under an account holder

Not supported: Does not handle card payment processing, BIN lookup, settlement, or report generation - use for Adyen for Platforms structural configuration only.

Use Cases

Patterns agents use Adyen Configuration 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 your Jentic One instance.

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 Jentic?

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

Credential isolation

Your Adyen X-API-Key, basic auth, and clientKey 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.

Intent-based discovery

Agents search Jentic by intent such as 'create an adyen balance account' or 'add a transaction rule', and Jentic returns the matching Configuration API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

Time to first call

FAQs

Specific to using Adyen Configuration 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.

Can I limit what my agent is allowed to do with the Adyen Configuration API?

Yes. Jentic One is self-hosted, so your own rules decide which Configuration API operations and credentials your agent may use. Because the account holder id sits in the URL path (/accountHolders/{id}), you can pin the agent to a single account holder and let it read and patch only that holder. You also pick the exact operations it may call, so card issuance via POST /paymentInstruments and rule writes via POST /transactionRules stay off limits unless you grant them.

Adyen Configuration API

Connect the Adyen Configuration API to your agent

Capabilities

Start building with Adyen Configuration API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs