ComplyAdvantage API

Name: ComplyAdvantage API API
Brand: ComplyAdvantage API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentIdentity AuthIdentity VerificationapiKey13 EndpointsREST

For Agents

Run AML searches against sanctions, PEP, watchlist, and adverse-media data, then monitor each search for new hits and track case decisions through entities, comments, and tags.

Quickstart

Get started with ComplyAdvantage 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:
"run an AML sanctions and PEP check on a customer"

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

Capabilities

What an agent can do with ComplyAdvantage API API.

Run an AML search against sanctions, PEP, watchlist, and adverse-media datasets for a named individual or entity

Retrieve detailed match data and source-level evidence for a search result

Enable ongoing monitoring on a search so new hits trigger alerts

Acknowledge monitor alerts to mark them reviewed

GET STARTED

Start building with ComplyAdvantage API API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI document for ComplyAdvantage API, keeping it validated and agent-ready.

Jentic publishes the only available OpenAPI specification for ComplyAdvantage API, keeping it validated and agent-ready. The ComplyAdvantage API automates anti-money-laundering screening against sanctions, politically exposed persons, watchlists, and adverse media. It is built around named search jobs that return matched entities, supports ongoing monitoring of those searches, and lets compliance teams acknowledge alerts, comment on cases, and tag results. Regional endpoints are available in the EU, US, and APAC for data-residency requirements.

Use Cases

Patterns agents use ComplyAdvantage API API for, with concrete tasks.

★ Customer Onboarding AML Screening

Screen every new customer against sanctions, PEP, watchlist, and adverse-media data at the point of onboarding. The /searches endpoint creates a named search and returns matches with source evidence; investigators then use comments and tags on the search to record their decision. Fintech, banking, and crypto onboarding flows use this to satisfy KYC and AML obligations before account opening.

Create a search named 'Acme Trading Ltd' against sanctions and PEP datasets, fetch the matched entities, and tag the search 'review' if any matches are returned

Ongoing Customer Monitoring

Keep onboarded customers under continuous AML watch so changes in sanctions, PEP, or adverse-media status are detected without re-running screening manually. Calling /searches/{id}/monitors enables monitoring on a search, and the acknowledge endpoint lets investigators clear alerts as they triage them. This supports the periodic-review obligations under FATF, FCA, and FinCEN guidance.

Enable monitoring on search id 12345, then list all unacknowledged monitor alerts created in the last 7 days

Investigator Case Workflow

Drive a small case-management workflow on top of the search records. Investigators can attach comments via /searches/{id}/comments, apply tags such as 'pending', 'cleared', or 'sar-filed' via /searches/{id}/tags/{tagName}, and inspect details via /searches/{id}/details. Compliance teams use this to keep audit trails inside ComplyAdvantage rather than exporting to a separate ticketing system.

For each search tagged 'pending' for more than 5 days, post an investigator comment 'reminder: review pending' and list the search ids

Agent-Driven AML Triage via Jentic

Let an AI agent triage AML alerts by running the appropriate search, summarizing match evidence, and applying the right tag based on a configurable rule. Through Jentic the agent searches by intent, loads the schema for the relevant ComplyAdvantage operation, and executes the call without the developer wiring auth or pagination. This compresses the manual triage step that compliance teams typically carry.

Given a new customer 'Maria Hernandez', create a search, summarize any matched entities in two lines, and tag the search 'auto-cleared' if zero matches

Key Endpoints

13 endpoints — jentic publishes the only available openapi specification for complyadvantage api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/searches

Create an AML search against selected datasets

GET

/searches/{id}

Retrieve a search and its summary

GET

/searches/{id}/details

Retrieve detailed match evidence for a search

GET

/searches/{id}/entities

List matched entities for a search

PATCH

/searches/{id}/monitors

Enable or disable ongoing monitoring on a search

PATCH

/searches/{id}/monitor/acknowledge

Acknowledge monitor alerts

POST

/searches/{id}/comments

Add an investigator comment to a search

PUT

/searches/{id}/tags/{tagName}

Apply a tag to a search

POST

/searches

Create an AML search against selected datasets

GET

/searches/{id}

Retrieve a search and its summary

GET

/searches/{id}/details

Retrieve detailed match evidence for a search

GET

/searches/{id}/entities

List matched entities for a search

PATCH

/searches/{id}/monitors

Enable or disable ongoing monitoring on a search

Why though Jentic?

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

Credential isolation

ComplyAdvantage API keys are stored encrypted in the Jentic vault and injected as the Authorization header in 'Token YOUR_API_KEY' format at execution time. The raw key never enters the model context or application logs.

Intent-based discovery

Agents search Jentic with intents like 'run an AML check on a customer' and Jentic returns the matching ComplyAdvantage operation with its parameter schema, so the agent can call POST /searches without browsing developer docs.

Time to first call

Direct integration: 2-3 days for auth, search creation, monitor configuration, and alert handling. Through Jentic: under 1 hour via search, load, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

OpenSanctions

Open dataset of sanctions, PEP, and watchlist entries with a free tier

Choose OpenSanctions when you need raw sanctions and PEP data without the case-management workflow and want a permissive open-data licence.

Complementary

Onfido

Document and biometric identity verification

Use Onfido alongside ComplyAdvantage when onboarding requires document and selfie verification in addition to sanctions and PEP screening.

Complementary

Persona

Configurable identity verification and KYC orchestration

Use Persona to orchestrate the wider KYC flow and call ComplyAdvantage as the AML data source within it.

FAQs

Specific to using ComplyAdvantage API API through Jentic.

Why is there no official OpenAPI spec for ComplyAdvantage API?

ComplyAdvantage does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call ComplyAdvantage API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the ComplyAdvantage API use?

The API uses an API key passed in the Authorization header in the form 'Token YOUR_API_KEY'. Through Jentic the key is stored encrypted in the vault and injected at execution time, so the raw key never enters the agent's prompt or logs. All requests must be made over HTTPS.

Can I enable ongoing monitoring on an AML search?

Yes. After creating a search via POST /searches, call PATCH /searches/{id}/monitors to enable monitoring on that search. New matches generate alerts that you clear with PATCH /searches/{id}/monitor/acknowledge.

What are the rate limits for the ComplyAdvantage API?

ComplyAdvantage applies tenant-specific rate limits, commonly 100 requests per second per API key with bulk-search throttling. The exact limit depends on your contract; agents should add backoff on HTTP 429 and Jentic surfaces these as structured errors rather than retrying silently.

How do I run a sanctions search through Jentic?

Run the Jentic search query 'run an AML sanctions check', load the returned operation (POST /searches), and execute it with the search term and dataset filters. Then call GET /searches/{id}/entities to fetch the matched entities.

Which regions can I host my data in?

ComplyAdvantage offers three regional endpoints: api.complyadvantage.com (EU), api.us.complyadvantage.com (US), and api.ap.complyadvantage.com (APAC). Pick the endpoint that matches your data-residency obligations and use the same one consistently.