ComplyAdvantage

AML screening and ongoing monitoring with PEP, sanctions, and adverse media checks.

Detail	Value
Category	iGaming
Base URL	https://api.complyadvantage.com
Authentication	API Key
Endpoints	10
Connector key	complyadvantage

Using ComplyAdvantage in a workflow

1. Go to Connections and click New Connection.
2. Pick ComplyAdvantage from the marketplace.
3. Enter your credentials (see Authentication above for what's expected).
4. In a workflow, drop an API Call node and select this connection.
5. Pick the operation you need from the Operation dropdown — the full list is below.

Available endpoints

Endpoint	Summary
POST /searches	Create AML screening search
GET /searches	List search history
GET /searches/{id}	Get search overview
GET /searches/{id}/details	Full search results
PATCH /searches/{id}	Update search
PATCH /searches/{id}/entities	Update entity status
GET /searches/{id}/monitors	Get monitoring config
PATCH /searches/{id}/monitors	Enable/disable monitoring
GET /searches/{id}/monitor/differences	Monitoring alerts
GET /searches/{id}/certificate	Compliance certificate

Each endpoint is documented in full below. Use the outline on the right to jump to one.

POST /searches

Create AML screening search

Detail	Value
Operation ID	aml.createSearch
Method	POST
Path	/searches

Parameters

No parameters.

Request Body

Field	Type
search_term	string
fuzziness	number
filters	object

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your ComplyAdvantage connection from the Connection dropdown.
3. In the Operation dropdown, select aml.createSearch.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

Required fields are marked — fill them or the call will fail at runtime.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream ComplyAdvantage API reference.

GET /searches

List search history

Detail	Value
Operation ID	aml.listSearches
Method	GET
Path	/searches

Parameters

No parameters.

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your ComplyAdvantage connection from the Connection dropdown.
3. In the Operation dropdown, select aml.listSearches.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream ComplyAdvantage API reference.

GET /searches/{id}

Get search overview

Detail	Value
Operation ID	aml.getSearch
Method	GET
Path	/searches/{id}

Parameters

Name	Location	Type	Required
id	path	string	Yes

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your ComplyAdvantage connection from the Connection dropdown.
3. In the Operation dropdown, select aml.getSearch.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

Required fields are marked — fill them or the call will fail at runtime.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream ComplyAdvantage API reference.

GET /searches/{id}/details

Full search results

Detail	Value
Operation ID	aml.getSearchDetails
Method	GET
Path	/searches/{id}/details

Parameters

Name	Location	Type	Required
id	path	string	Yes

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your ComplyAdvantage connection from the Connection dropdown.
3. In the Operation dropdown, select aml.getSearchDetails.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

Required fields are marked — fill them or the call will fail at runtime.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream ComplyAdvantage API reference.

PATCH /searches/{id}

Update search

Detail	Value
Operation ID	aml.updateSearch
Method	PATCH
Path	/searches/{id}

Parameters

Name	Location	Type	Required
id	path	string	Yes

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your ComplyAdvantage connection from the Connection dropdown.
3. In the Operation dropdown, select aml.updateSearch.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

Required fields are marked — fill them or the call will fail at runtime.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream ComplyAdvantage API reference.

PATCH /searches/{id}/entities

Update entity status

Detail	Value
Operation ID	aml.updateEntityStatus
Method	PATCH
Path	/searches/{id}/entities

Parameters

Name	Location	Type	Required
id	path	string	Yes

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your ComplyAdvantage connection from the Connection dropdown.
3. In the Operation dropdown, select aml.updateEntityStatus.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

Required fields are marked — fill them or the call will fail at runtime.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream ComplyAdvantage API reference.

GET /searches/{id}/monitors

Get monitoring config

Detail	Value
Operation ID	aml.getMonitoringConfig
Method	GET
Path	/searches/{id}/monitors

Parameters

Name	Location	Type	Required
id	path	string	Yes

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your ComplyAdvantage connection from the Connection dropdown.
3. In the Operation dropdown, select aml.getMonitoringConfig.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

Required fields are marked — fill them or the call will fail at runtime.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream ComplyAdvantage API reference.

PATCH /searches/{id}/monitors

Enable/disable monitoring

Detail	Value
Operation ID	aml.updateMonitoring
Method	PATCH
Path	/searches/{id}/monitors

Parameters

Name	Location	Type	Required
id	path	string	Yes

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your ComplyAdvantage connection from the Connection dropdown.
3. In the Operation dropdown, select aml.updateMonitoring.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

Required fields are marked — fill them or the call will fail at runtime.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream ComplyAdvantage API reference.

GET /searches/{id}/monitor/differences

Monitoring alerts

Detail	Value
Operation ID	aml.getMonitoringAlerts
Method	GET
Path	/searches/{id}/monitor/differences

Parameters

Name	Location	Type	Required
id	path	string	Yes

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your ComplyAdvantage connection from the Connection dropdown.
3. In the Operation dropdown, select aml.getMonitoringAlerts.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

Required fields are marked — fill them or the call will fail at runtime.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream ComplyAdvantage API reference.

GET /searches/{id}/certificate

Compliance certificate

Detail	Value
Operation ID	aml.getComplianceCertificate
Method	GET
Path	/searches/{id}/certificate

Parameters

Name	Location	Type	Required
id	path	string	Yes

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your ComplyAdvantage connection from the Connection dropdown.
3. In the Operation dropdown, select aml.getComplianceCertificate.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

Required fields are marked — fill them or the call will fail at runtime.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream ComplyAdvantage API reference.