Sanctions

PEP and Sanction Bulk Search API

PEP and Sanction Bulk Search runs the PEP and Sanction Search for a list of subjects in a single call. One set of search settings applies to every subject, and each subject is answered on its own, so a customer file can be screened in one pass.

Each subject is an individual, a company or a vessel, screened against the same PEP and sanction sources as the single search
One strictness level, similarity threshold and set of country filters for the whole batch, with a check_id echoed on each result

Get API access Talk to us

For developers

After the technical detail?

For the technical detail, go to the API documentation. It holds the request and response schema, the integration guides and the error codes for this endpoint.

Request and response schema
Search types and sandbox records

View developer documentation

Accounts start in the sandbox. Production keys are issued once the account is approved.

Encrypted in transit and at rest Handled under the Australian Privacy Principles

What the check gives you

Screening a customer file against PEP and sanction lists in one pass

Periodic re-screening of a customer base does not suit one call per customer. PEP and Sanction Bulk Search takes a list of subjects in one request, applies the same strictness, threshold and country filters to each, and returns a result for every one. Each result carries the same matches as a single search, so the evidence can be written back to each customer record in one operation.

A result for every subject sent

The results array holds one item per request item. Each carries its own list of matches, each flagged as PEP, sanctioned or both, with the sources and the similarity score.

Your own reference on each result

A check_id supplied on a request item is echoed on the matching result, so each answer lands against the right customer record.

One policy for the whole batch

The search type, PEP and sanction countries, maximum results, similarity threshold and extended-result flag are set once and applied to every subject.

A subject with no listing does not fail the batch

A subject with no match at the chosen strictness returns an empty match list. The rest of the batch is answered as normal.

How a check runs

Many subjects in, one answer per subject out

The list is sent as one request. Each subject is screened on its own and the results come back together in the same response.

Each request item carries the subject's names and date of birth, or a company or vessel name, and optionally a check_id. The reference documentation does not state a maximum number of items per request.

What it costs

A monthly subscription, drawn down as you run checks

Your subscription is credited to your account each month and each check consumes credits from it. If you go past the included amount, further checks are charged at a per-check rate. The rate depends on the volume you commit to, so the sales team is the fastest way to find where your business lands.

Volume-based pricing
No lock-in contract

How billing works

Subscribe monthly, spend it as credits

The monthly subscription arrives as credits on your account.
Each check draws down credits as it runs.
Checks beyond the included credits are billed per check.
Higher monthly volume moves you to a lower rate.

Talk to sales about volume

Related checks

Others in Sanctions

PEP and Sanction Search is the single-subject form of this check.

PEP / Sanction Search API

All Sanctions endpoints

Questions

Questions we get asked about PEP and Sanction Bulk Search

Do we need a developer to implement this?

Yes. The endpoint takes a JSON array of subjects and returns a JSON array of results, so a developer connects it to your data pipeline or re-screening job. A sandbox with a deterministic test dataset is provided at no usage cost, so the integration can be built and tested before production keys are issued.

What does our system need to send?

The shared settings: search type, optional PEP and sanction country codes, maximum results, similarity threshold and the extended-result flag. Then a requests array where each item carries an individual's first and last name, or full name, with optional middle name and date of birth, or a company name, or a vessel name, and optionally a check_id.

What comes back for each subject?

The check_id from the request and a list of matches. Each match carries the is_pep and is_sanctioned flags, the sanction countries, the PEP and sanction sources, the matched name and its similarity score, and extended data where requested.

How large a file can we process?

The reference documentation does not state a maximum number of subjects per request. The API allows 600 requests per minute by default, measured as a rolling average, and returns a 429 response above that rate. A higher limit can be requested through Global Data support.

Are the names we send stored by Global Data?

Personally identifiable information sent in a request is not stored or retained unless it is needed to process that request. Query data is stripped of PII before it is kept for audit. Data in transit and at rest is encrypted, and retention follows the Australian Privacy Act and the Australian Privacy Principles. Global Data is not a credit bureau and does not create an access footprint on any record.

Getting started

The first step to access is a conversation

New accounts begin with sandbox access, and production API keys are issued once the account has been commercially approved.

Get API access Talk to us

Call 03 9948 4089, 9am–5pm AEST Monday to Friday

Encrypted in transit and at rest

Handled under the Australian Privacy Principles

ISO 27001 Certified