Adyen Legal Entity Management API

Name: Adyen Legal Entity Management API
Brand: Adyen Legal Entity Management API
Availability: InStock

✓ Official Vendor SpecIdentity AuthIdentity VerificationapiKey, basic33 Endpoints

Install Jentic One Beta

Connect the Adyen Legal Entity Management API to your agent

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

Create legal entities of type individual, organization, sole proprietorship, or trust with required verification fields

Attach and update business lines that describe the products and services a legal entity offers

Upload, replace, and delete verification documents (passport, bank statement, registration document) tied to a legal entity

GET STARTED

Start building with Adyen Legal Entity Management API

Explore with Jentic

View OpenAPI Document

For Agents

Create and update legal entities, attach business lines and transfer instruments, upload verification documents, and run hosted onboarding for Adyen Balance Platform and Issuing accounts.

Use for: I need to create a legal entity for a new business signing up to my platform, Update the business line of an existing legal entity, Upload a passport document for a legal entity director, Get the verification errors blocking a legal entity from going live

Not supported: Does not handle payment authorisation, balance transfers, or issuing card programs - use for legal entity, business line, and verification document management only.

Use Cases

Patterns agents use Adyen Legal Entity Management API for, with concrete tasks.

★ Modern Marketplace Onboarding

Onboard new sellers on a marketplace running on Adyen's Balance Platform by creating legal entities, attaching business lines that describe the products sold, and uploading verification documents. The /legalEntities, /businessLines, and /documents endpoints together model the full KYC and KYB picture; /checkVerificationErrors surfaces what is still missing before the entity can transact.

POST /legalEntities with type Organization and registered business details, then POST /businessLines with the merchant category code and call /legalEntities/{id}/checkVerificationErrors to surface remaining gaps

Hosted KYC for Account Holders

Use the legal entity hosted onboarding endpoints to redirect account holders into an Adyen-hosted page where they complete verification fields and upload documents. Suitable for platforms that prefer not to build a bespoke KYC UI. The platform creates the legal entity, requests a hosted onboarding URL, and receives back a link that walks the legal entity contact through the missing requirements.

Create the legal entity, then POST to the hosted onboarding endpoint to generate the URL and email it to the legal entity contact for completion

Document Lifecycle and Re-verification

Manage the full document lifecycle for a legal entity: upload an initial document via POST /documents, replace it with PATCH /documents/{id} when it expires, and delete it once verification is no longer required. The transfer instruments resource lets you attach and update bank accounts on the same legal entity, and /checkVerificationErrors highlights which documents remain outstanding at any time.

POST /documents with type bankStatement and base64 content for legal entity LEM-0421, then call /legalEntities/LEM-0421/checkVerificationErrors to confirm the bank verification gap is cleared

AI Agent Compliance Operations

Compliance agents create and update legal entities through Jentic without raw access to the Adyen API key. The agent searches for 'create a legal entity on Adyen' via Jentic, receives the /legalEntities schema with the required type and entity-specific fields, and executes the call. Subsequent document uploads and verification error checks follow the same search-load-execute pattern with vaulted credentials.

Search Jentic for 'check Adyen legal entity verification errors', load the schema, and POST /legalEntities/{id}/checkVerificationErrors for the legal entity referenced in the compliance ticket

Key Endpoints

33 endpoints — manage legal entities, business lines, transfer instruments, and verification documents on adyen's modern balance platform and issuing integrations.

METHOD

PATH

DESCRIPTION

POST

/legalEntities

Create a legal entity

GET

/legalEntities/{id}

Get a legal entity

PATCH

/legalEntities/{id}

Update a legal entity

POST

/businessLines

Create a business line

POST

/documents

Upload a verification document

POST

/legalEntities/{id}/checkVerificationErrors

Check verification errors on a legal entity

POST

/transferInstruments

Create a transfer instrument such as a bank account

GET

/legalEntities/{id}/businessLines

List business lines for a legal entity

POST

/legalEntities

Create a legal entity

GET

/legalEntities/{id}

Get a legal entity

PATCH

/legalEntities/{id}

Update a legal entity

POST

/businessLines

Create a business line

POST

/documents

Upload a verification document

POST

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 'create a legal entity on adyen' or 'check verification errors', and Jentic returns the matching Legal Entity Management 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 Legal Entity Management API through Jentic.

What authentication does the Adyen Legal Entity Management API use?

The Legal Entity 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 Customer Area or Balance Platform Customer Area for Issuing integrations. Through Jentic, your X-API-Key is held encrypted in your Jentic One instance and agents authenticate with scoped tokens, keeping the raw key out of agent context.

Can I support both individuals and organisations through this API?

Yes. POST /legalEntities accepts a type field with values individual, organization, soleProprietorship, or trust, and the request body shape changes accordingly. Individuals require personal details such as name and date of birth; organisations require registered name, registration number, and legal address. Verification requirements vary by type and jurisdiction.

What are the rate limits for the Legal Entity Management API?

Adyen applies per-merchant rate limits in the tens of requests per second for legal entity operations on production, lower in test. Document uploads have lower limits because of payload size. Excess requests return HTTP 429; back off and retry, and contact your Adyen account manager if you need a sustained higher ceiling.

How do I check verification errors through Jentic?

Search Jentic for 'check Adyen legal entity verification errors' to find the POST /legalEntities/{id}/checkVerificationErrors operation. Pass the legal entity id in the path and Jentic returns the schema and executes the call with vaulted credentials. The response highlights which fields or documents still need attention. Run it through Jentic One, the self-hosted execution layer.

What document types can I upload for verification?

POST /documents accepts a documentType field with values such as passport, driversLicense, identityCard, bankStatement, registrationDocument, and proofOfResidence. Documents are uploaded as base64-encoded content with metadata describing the legal entity and document subject. The exact accepted set varies by entity type and jurisdiction; the spec enumerates the supported values.

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

Yes. Jentic One is self-hosted by you, so your own rules decide which operations and credentials the agent may use. Because the legal entity id sits in the URL path (/legalEntities/{id}), you can pin an agent to a single legal entity and allow only read, PATCH, and POST /legalEntities/{id}/checkVerificationErrors on it. Write operations such as POST /documents or POST /transferInstruments stay off unless you explicitly add them, and your encrypted X-API-Key is injected at execution time rather than exposed to the agent.

Adyen Legal Entity Management API

Connect the Adyen Legal Entity Management API to your agent

Capabilities

Start building with Adyen Legal Entity Management API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs