OpenSanctions

Sanctions and PEP screening for iGaming compliance with entity search and fuzzy matching.

Detail	Value
Category	iGaming
Base URL	https://api.opensanctions.org
Authentication	API Key
Endpoints	7
Connector key	opensanctions

Using OpenSanctions in a workflow

1. Go to Connections and click New Connection.
2. Pick OpenSanctions 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
GET /search/{dataset}	Full-text entity search
POST /match/{dataset}	Fuzzy entity matching
GET /entities/{entity_id}	Get entity by ID
GET /entities/{entity_id}/adjacent	Related entities
GET /catalog	List datasets
GET /datasets/{dataset}	Dataset metadata
GET /reconcile/{dataset}	OpenRefine reconciliation

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

GET /search/{dataset}

Full-text entity search

Detail	Value
Operation ID	igaming.searchEntities
Method	GET
Path	/search/{dataset}

Parameters

Name	Location	Type	Required
dataset	path	string	Yes
q	query	string	No

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your OpenSanctions connection from the Connection dropdown.
3. In the Operation dropdown, select igaming.searchEntities.
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 OpenSanctions API reference.

POST /match/{dataset}

Fuzzy entity matching

Detail	Value
Operation ID	igaming.matchEntities
Method	POST
Path	/match/{dataset}

Parameters

Name	Location	Type	Required
dataset	path	string	Yes

Request Body

Field	Type
queries	object

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your OpenSanctions connection from the Connection dropdown.
3. In the Operation dropdown, select igaming.matchEntities.
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 OpenSanctions API reference.

GET /entities/{entity_id}

Get entity by ID

Detail	Value
Operation ID	igaming.getEntity
Method	GET
Path	/entities/{entity_id}

Parameters

Name	Location	Type	Required
entity_id	path	string	Yes

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your OpenSanctions connection from the Connection dropdown.
3. In the Operation dropdown, select igaming.getEntity.
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 OpenSanctions API reference.

GET /entities/{entity_id}/adjacent

Related entities

Detail	Value
Operation ID	igaming.getAdjacentEntities
Method	GET
Path	/entities/{entity_id}/adjacent

Parameters

Name	Location	Type	Required
entity_id	path	string	Yes

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your OpenSanctions connection from the Connection dropdown.
3. In the Operation dropdown, select igaming.getAdjacentEntities.
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 OpenSanctions API reference.

GET /catalog

List datasets

Detail	Value
Operation ID	igaming.listDatasets
Method	GET
Path	/catalog

Parameters

No parameters.

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your OpenSanctions connection from the Connection dropdown.
3. In the Operation dropdown, select igaming.listDatasets.
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 OpenSanctions API reference.

GET /datasets/{dataset}

Dataset metadata

Detail	Value
Operation ID	igaming.getDataset
Method	GET
Path	/datasets/{dataset}

Parameters

Name	Location	Type	Required
dataset	path	string	Yes

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your OpenSanctions connection from the Connection dropdown.
3. In the Operation dropdown, select igaming.getDataset.
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 OpenSanctions API reference.

GET /reconcile/{dataset}

OpenRefine reconciliation

Detail	Value
Operation ID	igaming.reconcile
Method	GET
Path	/reconcile/{dataset}

Parameters

Name	Location	Type	Required
dataset	path	string	Yes

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your OpenSanctions connection from the Connection dropdown.
3. In the Operation dropdown, select igaming.reconcile.
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 OpenSanctions API reference.