Adyen Management API (v3)

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

✓ Official Vendor SpecDeveloper ToolsMonitoring ObservabilityapiKey, basic134 EndpointsREST

For Agents

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

Quickstart

Get started with Adyen Management API (v3) 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 an Adyen webhook subscription on v3"

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

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

Configure payment methods on merchant accounts and approve or disable them per channel

GET STARTED

Start building with Adyen Management API (v3) API

Explore with Jentic

View OpenAPI Document

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

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 the Jentic vault, 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 though Jentic?

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

Credential isolation

Adyen X-API-Key credentials are stored encrypted in the Jentic MAXsystem vault. Agents call /companies/{companyId}/* and merchant-level operations through scoped tokens, so the raw API key never enters agent prompts or logs.

Intent-based discovery

Agents search by intent ('list Adyen merchants', 'create a webhook subscription', 'upload an Android app') and Jentic returns the matching Management API v3 operation with its full request schema and parameter validation.

Time to first call

Direct integration: 3-7 days for auth, credential lifecycle, webhook setup, Android app upload pipeline, and merchant audit logic. Through Jentic: under 1 hour per operation — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Adyen Management API (v1)

The earlier v1 surface of the same Management API

Choose v3 for new integrations; v1 is only relevant when extending an existing integration that already targets v1

Complementary

Adyen Management Webhooks

Webhook payload spec for events on Management API resources

Use the Management API to create webhook subscriptions and the Management Webhooks spec to parse the resulting events

Complementary

Adyen Checkout API

Processes payments on merchant accounts configured through Management

Use Management to provision merchant accounts and Checkout to process payments on those accounts

Alternative

Stripe API

Stripe's account and webhook configuration is exposed through resources on the main Stripe API

Choose Stripe when your processor is Stripe and configuration is part of the same API; choose Adyen Management v3 for Adyen accounts

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 the MAXsystem vault 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. Sign up at https://app.jentic.com/sign-up to get started.

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.