Adyen Management API (v3)

Name: Adyen Management API (v3) API
Brand: Adyen Management API (v3)
Availability: InStock

✓ Official Vendor SpecDeveloper ToolsMonitoring ObservabilityapiKey, basic134 Endpoints

Install Jentic One Beta

Connect the Adyen Management API (v3) to your agent

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

Manage company and merchant accounts including listing, retrieval, and configuration updates

Provision and rotate API credentials, API keys, client keys, and allowed origins

Upload and reprocess Android apps and Android certificates used by payment terminals

GET STARTED

Start building with Adyen Management API (v3) API

Explore with Jentic

View OpenAPI Document

For Agents

Programmatically configure Adyen merchant accounts, stores, terminals, payment methods, API credentials, and webhooks on the actively maintained v3 Management API.

Use for: I need to upload an Android app for use on Adyen terminals, Create a webhook subscription on a merchant account, List all merchant accounts under a company on v3, Generate a new API key for an API credential

Not supported: Does not handle payment authorisation, balance transfers, or chargeback responses - use for company, merchant, store, terminal, and webhook configuration only.

Use Cases

Patterns agents use Adyen Management API (v3) API for, with concrete tasks.

★ Greenfield Platform Configuration

Set up an Adyen platform from scratch using v3, the actively evolving Management API surface. Provision the company, create merchant accounts, configure payment methods, set up webhook subscriptions, and provision API credentials with allowed origins, all from infrastructure-as-code or a platform admin tool. Suitable for new integrations that want to avoid the Customer Area UI for first-line configuration.

POST a new merchant account under companyId, configure its payment methods, create a webhook subscription, and provision an API credential with the appropriate allowed origins

Android App and Terminal Lifecycle

Upload Android apps and certificates for distribution to Adyen payment terminals through v3, which exposes the upload patterns directly on the Management API. Manage app reprocessing on validation failures and assign apps to terminals through the related operations. Suitable for retailers building custom POS apps that run on Adyen Android terminals.

POST /companies/{companyId}/androidApps with the APK metadata, then PATCH the app to reprocess if validation surfaces fixable issues

Multi-Merchant Configuration Audit

Run periodic audits across a company hierarchy by listing merchants, stores, payment methods, and webhook subscriptions on v3 and comparing the live configuration against the platform's source-of-truth. The Management API surface makes this practical without scraping the Customer Area, and the v3 endpoints stay in sync with new Adyen features as they ship. Useful for platforms with many merchants where configuration drift causes payment failures.

List all merchants under companyId, then for each merchant fetch payment methods and webhook subscriptions and write the diff against the source-of-truth into the audit table

AI Agent Platform Operations

Operations agents change Adyen configuration on v3 through Jentic without holding raw API keys. The agent searches Jentic for 'create Adyen webhook subscription' or 'upload Adyen Android app', receives the matching Management API v3 operation schema, and executes the call. Credentials remain isolated in your Jentic One instance, so the raw API key never reaches the agent context.

Search Jentic for 'create Adyen webhook subscription on v3', load the schema, and POST /companies/{companyId}/webhooks with the receiver URL and event types from the configuration ticket

Key Endpoints

134 endpoints — configure 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.

METHOD

PATH

DESCRIPTION

GET

/companies/{companyId}/merchants

List merchant accounts under a company

POST

/companies/{companyId}/androidApps

Upload an Android app for terminals

POST

/companies/{companyId}/androidCertificates

Upload an Android certificate

POST

/companies/{companyId}/apiCredentials

Create a company-level API credential

POST

/companies/{companyId}/apiCredentials/{apiCredentialId}/generateApiKey

Generate a new API key for an API credential

GET

/companies/{companyId}/webhooks

List webhook subscriptions on a company account

GET

/companies/{companyId}

Get a company account

GET

/companies/{companyId}/merchants

List merchant accounts under a company

POST

/companies/{companyId}/androidApps

Upload an Android app for terminals

POST

/companies/{companyId}/androidCertificates

Upload an Android certificate

POST

/companies/{companyId}/apiCredentials

Create a company-level API credential

POST

/companies/{companyId}/apiCredentials/{apiCredentialId}/generateApiKey

Generate a new API key for an API credential

Why Jentic?

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

Credential isolation

Your Adyen X-API-Key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'list adyen merchants' or 'create a webhook subscription', and Jentic returns the matching Management API v3 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 Management API (v3) API through Jentic.

What authentication does the Adyen Management API v3 use?

The Management API accepts an API key in the X-API-Key header or HTTP Basic authentication with web service user credentials. Generate the key from your Adyen Customer Area and grant it the management roles you need. Through Jentic, the X-API-Key value is held encrypted in your Jentic One instance and agents authenticate with scoped tokens, so the raw key never enters agent context.

What does v3 add over v1 of the Management API?

Version 3 is the actively maintained version and reflects new Adyen features as they ship. Notable differences include POST endpoints for uploading Android apps (POST /companies/{companyId}/androidApps) and Android certificates (POST /companies/{companyId}/androidCertificates) which are absent on v1. Total endpoint count is 134 on v3 vs 130 on v1, with v3 receiving ongoing additions.

What are the rate limits for the Management API on v3?

Adyen applies per-company rate limits typically in the tens of requests per second for management operations on production. Bulk audits and migrations should batch work and back off on HTTP 429 responses. Contact your Adyen account team if you need a sustained higher ceiling for large platform migrations.

How do I create a webhook subscription through Jentic?

Search Jentic for 'create Adyen webhook subscription on v3' to find the POST /companies/{companyId}/webhooks operation. Required fields are the company id in the path, plus the webhook url, type, and event types in the body. Jentic loads the schema and executes with vaulted credentials. Run it through Jentic One, the self-hosted execution layer.

Can I upload Android apps for terminals through this API?

Yes, on v3. POST /companies/{companyId}/androidApps uploads the app package with metadata, and PATCH on the resulting Android app id triggers reprocessing if validation surfaces fixable issues. Android certificates follow the same pattern via POST /companies/{companyId}/androidCertificates. These create operations exist on v3 but not on v1.

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

Yes. Because you run Jentic One yourself, your own rules decide which operations and credentials the agent may use, and you pick exactly which Management v3 endpoints it can call. Since v3 carries the companyId in the URL path (/companies/{companyId}/...), a rule can pin the agent to a single company so it lists that company's merchants and webhooks and nothing more. You can also keep sensitive operations such as API credential and API-key generation off the agent's list, so they stay out of reach unless you explicitly add them.

Adyen Management API (v3)

Connect the Adyen Management API (v3) to your agent

Capabilities

Start building with Adyen Management API (v3) API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs