Official EU Consolidated Sanctions List

Screen Persons Against
the EU Sanctions List
– functional demo

Manual person verification and REST API access for onboarding, compliance workflows, and business software integrations.

EU Flag Official EU data source
🔌 REST API
🔒 Data-minimized processing
⚡ Real-time response
1 API
endpoint
Single integration point for manual checks and automated workflows
XML
Structured response with match flag and detail field
EU
official
Data sourced from the official EU consolidated sanctions list
🏢
Customer Onboarding
Screen customers and business partners before starting a commercial relationship.
🔄
Recurring Screening
Use the service in regular compliance checks and recurring review workflows.
🔌
System Integration
Connect sanctions screening to your CRM, ERP, onboarding tool, or internal application via REST API.
🔍
Manual Verification
Run quick ad-hoc checks directly in the browser without any integration work.

Programs

Free access is available for testing, evaluation and local development.
For API integration, higher limits and production use, registration or a paid plan is required.
Program – pricing plan identifier
Currency – billing currency for your plan
For custom pricing or higher limits, contact us. – Write to us.
Program Limit/day Price/query Currency Flat rate/mo Description
Loading…
Person Verification

Person Verification

Search Analysis
Technical transaction data is processed for usage limits, security and billing. Screening results are indicative only and should always be reviewed as part of your internal compliance process.

Current Data Version

Date: … File: … Filename: …

Result

…

File screening
Screen a file of persons Import JSON, XML, CSV or XLSX and download the screening result in the format you need.

Choose the source file

Use exactly these columns or fields: first_name, last_name, birth_date (YYYY-MM-DD), customer_id. XLSX data must be on the first worksheet.

No file selected.

Download an exact input template:

Check and download

The whole file is checked as one batch against the current EU consolidated sanctions list.

Select a file and output format.

This action uses the API token of the currently signed-in user. Sign in

Data protection
The source file is read locally in your browser and is not uploaded or stored as a file. Its persons are sent over HTTPS only for immediate screening. Neither the source nor the result is written to browser storage. The server transaction log contains only a random batch reference, item order and technical billing data; personal identifiers and dates of birth are not stored there. The exported file remains only on your device.
API Integration

API Integration Guide

Use the API endpoint to integrate EU sanctions screening directly into your application, onboarding flow, or compliance workflow.

Getting started:

  1. Free access is available with a limited daily quota for testing and evaluation.
  2. Registered access provides higher limits for development and initial integration.
  3. Paid plans are intended for production use and regular screening workflows.
  4. If your required volume exceeds the listed plans, contact us for a custom setup.
  5. Registration and commercial setup are available through the Navigation section.
  6. Open Navigation, select Show API token, sign in again, and copy the token while it is visible for 20 seconds.
  7. Replace the placeholder Bearer token with your copied API token.

What you get

  • Official EU consolidated sanctions data
  • Structured XML response per person
  • Match flag and detail field
  • Single endpoint for manual and automated workflows
  • Tiered access for evaluation, integration and production use

API endpoint: https://api.aaasoft.cz/sp_CheckPerson_XML · API documentation

Free example — screen 3 persons via curl:

No API token is required. Each person uses one daily check, so run this three-person example only if all 3 free checks are still available today. If fewer remain, the complete batch is rejected.

Download example JSON with 3 persons

curl.exe --fail-with-body --request POST "https://api.aaasoft.cz/sp_CheckPerson_XML" --header "Content-Type: application/json" --data-binary "@screening-example.json" --output "result.xml"

Run in a terminal window. The response will be saved to result.xml

The response is an XML file containing screening results for each queried person, including a match flag and a detail field.

Registered access with an API token:

curl.exe --fail-with-body --request POST "https://api.aaasoft.cz/sp_CheckPerson_XML" --header "Content-Type: application/json" --header "Authorization: Bearer YOUR_API_TOKEN" --data-binary "@screening-example.json" --output "result.xml"

Only an HTTP 200 response is a screening result. HTTP 429 means that the daily limit was exceeded and must not be interpreted as found=No.

Best regards,
Rapid Cluster Experience s.r.o.

Ready for production use?

Contact us to discuss pricing, API token setup, higher limits, or a custom integration plan for your organisation.