canonical: https://jentic.com/apis/adyen.com/adyen-management-service-v1 # Adyen Management API (v1) 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 1 of the Management API exposes 130 operations against /v1, covering company-level, merchant-level, and store-level configuration without requiring access to the Customer Area UI. New integrations should consider Management API v3, which is the actively evolving version. ## For AI agents Programmatically configure Adyen merchant accounts, stores, terminals, payment methods, API credentials, and webhooks across companies and merchants on the v1 Management API. ## Scope Does not handle payment authorisation, balance transfers, or chargeback responses - use for company, merchant, store, terminal, and webhook configuration only. ## Capabilities - Manage company and merchant accounts including listing, retrieval, and configuration updates - Provision and rotate API credentials, API keys, client keys, and allowed origins - Configure payment methods on merchant accounts and approve or disable them per channel - Manage stores under merchant accounts including creation, splits, and reference data - Manage payment terminal estates including assignment, settings, ordering, and Android apps - Create, update, and delete webhook subscriptions and rotate their HMAC keys - Manage users at company and merchant level including roles and access scopes ## Use cases ### Webhook and Credential Provisioning Provision API credentials and webhook subscriptions across an Adyen account hierarchy from infrastructure-as-code or a platform admin tool, rather than clicking through the Customer Area. The Management API v1 surface covers credential creation, API key rotation, allowed origin updates, and webhook subscription lifecycle on company and merchant accounts. Useful for platforms onboarding new merchants programmatically. Example prompt: POST a new API credential under companyId, then POST an allowed origin and call /generateApiKey to issue the key, finally storing it in the secrets manager ### Terminal Estate Management Manage a payment terminal estate at scale by listing terminals, assigning them to stores, updating settings, and inspecting Android apps and certificates installed on them. The Management API exposes the estate via company-level and merchant-level endpoints, so a retailer with many merchant accounts can centralise operations. Useful for retailers running thousands of terminals across stores and merchants. Example prompt: List terminals under merchantId, identify the unassigned ones, and assign each to its destination store using the matching Management API operation ### Multi-Merchant Configuration Audit Run periodic audits across a company hierarchy by listing merchants, stores, payment methods, and webhook subscriptions and comparing the live configuration against the platform's source-of-truth. The Management API's broad surface makes this practical without scraping the Customer Area. Useful for platforms with many merchants where configuration drift causes payment failures. Example prompt: List all merchants under companyId, then for each merchant fetch payment methods and webhooks, and write the diff against the source-of-truth into the audit table ### AI Agent Platform Operations Operations agents change Adyen configuration through Jentic without holding raw API keys. The agent searches Jentic for 'rotate Adyen API key' or 'create webhook subscription', receives the matching Management API operation schema, and executes the call. Credentials remain isolated in your Jentic One instance while the operation runs against the v1 surface. Example prompt: Search Jentic for 'list Adyen merchant accounts under a company', load the schema, and call /companies/{companyId}/merchants to feed the operations dashboard ## Key endpoints | Method | Path | Description | | --- | --- | --- | | GET | /companies/{companyId}/merchants | List merchant accounts under a company | | GET | /companies/{companyId}/apiCredentials | List company-level API credentials | | POST | /companies/{companyId}/apiCredentials/{apiCredentialId}/generateApiKey | Generate a new API key for an API credential | | POST | /companies/{companyId}/apiCredentials/{apiCredentialId}/allowedOrigins | Add an allowed origin to an API credential | | GET | /companies/{companyId}/webhooks | List webhook subscriptions on a company account | | GET | /companies/{companyId}/androidApps | List Android apps available to terminals under a company | | GET | /companies/{companyId} | Get a company account | ## Key resources - **Companies** — Top-level company accounts that contain merchants, users, and credentials - **Merchants** — Merchant accounts under a company with their own payment methods and stores - **Stores** — Locations under merchant accounts, used to scope terminals and reporting - **API Credentials** — Credential objects with API keys, client keys, and allowed origins - **Webhooks** — Webhook subscriptions for events on company or merchant accounts - **Terminals** — Payment terminals assigned to stores and merchants, including settings and apps - **Users** — Customer Area users at company and merchant level with role assignments ## Why Jentic - **Setup:** Wiring the Adyen Management API v1 by hand means handling its X-API-Key or basic auth, targeting the v1 management test host, and threading the companyId through a large configuration surface. Through Jentic you install once, import the Management API v1 from the API Directory, store the key once, and your agent calls it. - **Permission scoping:** Management v1 puts the companyId in the URL path (/companies/{companyId}/...), so a rule can pin your agent to one company: it can list that company's merchants, webhooks, and API credentials and nothing else. You choose the operations it may call, so API-key generation and allowed-origin writes stay out unless you add them. - **Credential handling:** 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. - **Discovery method:** Agents search Jentic by intent such as 'list adyen merchants' or 'rotate an API key', and Jentic returns the matching Management API operation with its input schema so the agent calls the right endpoint without browsing the reference docs. ## Related APIs - **Adyen Management API (v3)** — The actively evolving v3 of the same Management API surface - **Adyen Management Webhooks** — Webhook payload spec for events on Management API resources - **Adyen Checkout API** — Processes payments using merchant accounts configured through Management - **Stripe API** — Stripe's account and webhook configuration is exposed through resources on the main Stripe API ## FAQ ### What authentication does the Adyen Management API v1 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. ### Should I use Management API v1 or v3? Adyen actively evolves the Management API on v3, which is the recommended version for new integrations. Version 1 remains supported for existing integrations and exposes 130 endpoints across company, merchant, and store configuration. If your integration is greenfield, build against v3; if you already use v1, you can stay on it until you choose to migrate. ### What are the rate limits for the Management API? Adyen applies per-company rate limits typically in the tens of requests per second for management operations on production. Excess requests return HTTP 429 with a retry hint. Bulk audits should batch and back off, and your Adyen account team can raise limits for sustained higher volumes. ### How do I list a company's merchant accounts through Jentic? Search Jentic for 'list Adyen merchant accounts' to find the GET /companies/{companyId}/merchants operation. Pass the companyId in the path and Jentic loads the schema and executes with vaulted credentials. The response is paginated by Adyen so handle the page parameters where the merchant list is large. Run it through Jentic One, the self-hosted execution layer. ### Can I create webhook subscriptions through the Management API? Yes. The Management API exposes webhook subscription endpoints under /companies/{companyId}/webhooks (and the merchant-level equivalent) that create, update, list, and delete subscriptions. The Management Webhooks spec documents the payload format that the resulting subscription delivers to your receiver URL. ### Can I limit what my agent is allowed to do with the Adyen Management API? Yes. Because you run Jentic One self-hosted, your own rules decide which operations and credentials the agent may use, and the Management API v1 puts the companyId in every URL path (/companies/{companyId}/...), so a rule can pin your agent to a single company and its merchants, webhooks, and API credentials. You choose exactly which operations it may call, so sensitive writes like API-key generation and allowed-origin changes stay off unless you explicitly grant them. The encrypted Adyen key is injected only at execution time, so the agent acts within the scope you set without ever seeing the raw credential.