> For the complete documentation index, see [llms.txt](https://docs.complycube.com/documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.complycube.com/documentation/api-reference/static-data/screening-lists.md).

# Screening Lists

Retrieve AML screening lists for sanctions, watchlists, and other official sources used in screening checks.

This endpoint allows you to retrieve a list of all Sanctions and Watchlists available as part of a [Screening Check.](/documentation/api-reference/check-types/aml-screening-check.md) Typically, it enables users to create Screening Checks with [specific scopes](/documentation/api-reference/check-types/aml-screening-check.md#the-screeninglistsscope-object) in line with their KYC approach.

By default, all the lists are used when performing an **Extensive Screening Check**. Only a subset is used for a **Standard Screening Check**.

The lists are updated in real time, so the returned values are expected to change.

{% hint style="info" %}
**Politically Exposed Person (PEP)** and **Adverse Media** sources are not returned by this endpoint. These are identified through separate research-based processes and are reflected in AML screening results where applicable.
{% endhint %}

### URL

<mark style="color:blue;">**GET**</mark> `https://api.complycube.com/v1/static/screeningLists`

Retrieves all the screening lists in alphabetical order.

### Headers

<table><thead><tr><th width="281">Name</th><th width="99">Type</th><th>Description</th></tr></thead><tbody><tr><td><code>Authorization</code><mark style="color:red;">*</mark></td><td>string</td><td>The API <strong><code>live</code></strong> or <strong><code>test</code></strong> key</td></tr></tbody></table>

### Example request

{% tabs %}
{% tab title="cURL" %}

```bash
curl -X GET https://api.complycube.com/v1/static/screeningLists \
     -H 'Authorization: <YOUR_API_KEY>' 
```

{% endtab %}

{% tab title="Node.js" %}

```javascript
const { ComplyCube } = require("@complycube/api");

const complycube = new ComplyCube({ apiKey: "<YOUR_API_KEY>" });

const screeningLists = await complycube.static.listScreeningLists();
```

{% endtab %}

{% tab title="Python" %}

```python
from complycube import ComplyCubeClient

cc_api = ComplyCubeClient(api_key='<YOUR_API_KEY>')
          
result = cc_api.static.screening_lists()
```

{% endtab %}

{% tab title="PHP" %}

```php
use ComplyCube\ComplyCubeClient;

$ccapi = new ComplyCubeClient('<YOUR_API_KEY>');

$lists = $ccapi->screeningLists();
```

{% endtab %}

{% tab title=".NET" %}

```csharp
using ComplyCube.Net;
using ComplyCube.Net.Resources.Static;

var screeningListsApi = new StaticApi(new ComplyCubeClient("<YOUR_API_KEY>"));

var result = await screeningListsApi.ListScreeningListsAsync();
```

{% endtab %}
{% endtabs %}

### Example response

{% tabs %}
{% tab title="Success (200)" %}

```json
[
  "African Development Bank Group (AFDB) List of Debarred Entities",
  "DNB (Netherlands) Sanction Regulation 2006",
  "HM Treasury Consolidated List",
  "NYSE American Disciplinary Actions",
  "Singapore Police Force Commercial Crimes Prosecution List",
  ...
]
```

{% endtab %}
{% endtabs %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.complycube.com/documentation/api-reference/static-data/screening-lists.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.