Adyen Legal Entity Management API

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

✓ Official Vendor SpecIdentity AuthIdentity VerificationapiKey, basic33 EndpointsREST

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.

Quickstart

Get started with Adyen Legal Entity Management API 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 a legal entity on Adyen"

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

Capabilities

What an agent can do with Adyen Legal Entity Management API 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

Generate hosted onboarding links so legal entities can complete verification in an Adyen-hosted flow

GET STARTED

Start building with Adyen Legal Entity Management API API

Explore with Jentic

View OpenAPI Spec

Use Cases

Patterns agents use Adyen Legal Entity Management API 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 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 /legalEntities, /documents, and /businessLines through scoped tokens, so the raw API key never enters agent prompts or logs.

Intent-based discovery

Agents search by intent ('create a legal entity on Adyen', 'upload a verification document', 'check verification errors') and Jentic returns the matching Legal Entity Management operation with its full request schema.

Time to first call

Direct integration: 5-10 days for auth, legal entity and business line modelling, document upload pipeline, and verification error handling. Through Jentic: under 1 hour per operation — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

Adyen Management API

Configures the balance platform-level merchant settings the legal entities sit under

Use the Management API for platform configuration and the Legal Entity API for legal entity records and verification

Complementary

Adyen Checkout API

Authorises payments for merchants verified through the Legal Entity API

Use the Legal Entity API to onboard the merchant and Checkout to process its payments once verification clears

Alternative

Onfido API

Standalone identity verification provider with broad document and biometric coverage

Choose Onfido when you want a verification provider independent of your payment processor; choose Adyen Legal Entity when verification needs to integrate directly with the Adyen Balance Platform

Alternative

Sumsub API

KYC and KYB verification platform with hosted flows and SDK integration

Choose Sumsub for a full-stack verification provider with strong international coverage; choose Adyen Legal Entity when the verification record must live inside Adyen

FAQs

Specific to using Adyen Legal Entity Management API 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 the MAXsystem vault 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. Sign up at https://app.jentic.com/sign-up to get started.

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.