RESSOURCEN UND LEITFÄDEN · GUIDEUPDATED 2026-03-20
Ressourcen und Leitfäden
PEP-Screening-API-Integration: Leitfaden
PEP-Screening per REST-API in Ihre Plattform integrieren. Prüfen Sie politisch exponierte Personen, Sanktionen und Watchlists in Echtzeit.
If your team is embedding compliance checks in product flows, API integration quality is critical. This guide explains request structure, idempotency, retries, and evidence handling for PEP and sanctions screening APIs. Whether you are building KYC onboarding for a fintech, satisfying FATF Recommendation 12 requirements, or connecting to a personne politiquement exposée (PEP) database for EU compliance, a well-designed API integration is the foundation of scalable AML controls.
§01What this workflow covers
SCOPE- REST API with OpenAPI/Swagger specification for easy integration
- Real-time PEP screening with sub-second response times
- Coverage of global PEP databases across 200+ jurisdictions
- Combined PEP + sanctions + adverse media in a single API call
- Webhook support for async batch screening workflows
- SDKs available for Python, Node.js, and other languages
- Full audit trail with source citations for every screening decision
- ISO 27001-compliant infrastructure with 99.9% uptime SLA
§02Key statistics
DATA- Global PEP coverage
- Over 1.5 million PEPs and their associates are tracked across global databases
- ScreenVeritAI data coverage report
- API response time
- API-based PEP screening delivers results in <200ms — enabling real-time KYC at onboarding
- ScreenVeritAI API performance benchmarks
- Compliance efficiency
- KYC API integrations reduce manual compliance review time by up to 75%
- RegTech industry benchmarks
- Regulatory requirement
- FATF Recommendation 12 requires enhanced due diligence for all PEP relationships
- Financial Action Task Force
§03Compliance glossary
TERMS- PEP (Politically Exposed Person)
- An individual who holds or has held a prominent public position — such as a head of state, senior politician, or senior military officer — and their close associates and family members. PEPs require enhanced due diligence under FATF Recommendation 12.
- sanctions API
- A programmatic interface allowing software systems to screen names, entities, or transactions against official sanctions lists in real time.
- KYC (Know Your Customer)
- The process of verifying the identity of clients and assessing their suitability and risk profile, required under AML regulations globally.
- OpenAPI
- A standard specification format (formerly Swagger) for describing REST APIs, enabling automated documentation, SDK generation, and integration testing.
§04Authoritative references
SOURCES- 01FATF Recommendation 12 — Politically Exposed Persons
Financial Action Task Force
- 02OFAC SDN List API Access
U.S. Department of the Treasury
- 03EU PEP and Sanctions Compliance Requirements
European Commission
§05Expert perspective
NOTE“A well-integrated PEP screening API eliminates the bottleneck between compliance and customer onboarding — it's the difference between a 5-minute and a 5-day KYC process.”
“The API-first approach to PEP screening is now table stakes for any fintech or bank operating across multiple jurisdictions.”
§06Frequently asked questions
Q&A- What is a PEP screening API?
- A PEP screening API is a REST interface that allows software systems to check whether an individual is a Politically Exposed Person (PEP) — or associated with one — in real time. The API queries global PEP databases and returns a structured risk signal that compliance teams and automated workflows can act on immediately.
- How does ScreenVeritAI's PEP screening API work?
- Submit a name, date of birth, and optional country code via a POST request. The API runs fuzzy matching against global PEP lists, sanctions registers, and adverse media sources, then returns a scored result with source citations within milliseconds. A full OpenAPI/Swagger specification is available for integration testing and SDK generation.
- What data does the PEP API return?
- Each response includes the matched entity's name, PEP classification, associated sanctions entries, adverse media flags, source list identifiers, a match confidence score, and a timestamp. All fields are consistently typed and documented in the OpenAPI schema.
- How fast is the PEP screening API response time?
- Synchronous API calls return results in under 200ms for the vast majority of requests, enabling real-time PEP checks at the point of customer onboarding. Asynchronous batch endpoints with webhook callbacks are also available for high-volume workflows.
- Can the API screen for both PEP status and sanctions in one call?
- Yes. A single API call returns combined PEP, sanctions (OFAC SDN, EU, UN, UK OFSI, and others), and adverse media signals. This reduces latency and simplifies integration logic compared to calling separate endpoints for each dataset.
- What authentication does the PEP screening API use?
- The API uses scoped API keys passed via the Authorization header. Keys should be provisioned server-side with least-privilege permissions. Client-side key exposure is not supported. Key rotation and audit logs are available from the dashboard.
- Is the API compatible with OpenAPI/Swagger specifications?
- Yes. ScreenVeritAI publishes a full OpenAPI 3.0 specification for all endpoints. This enables automated SDK generation in Python, Node.js, Java, and other languages, as well as contract-based integration testing. The spec is available at /api/v1/openapi.json.
- How is PEP screening via API used in KYC and AML workflows?
- KYC teams trigger PEP checks at account onboarding, at material risk events (ownership changes, jurisdiction changes), and on a periodic re-screening schedule. AML workflows use the API response to gate account activation, escalate to human review, or feed risk scoring models. In French-speaking jurisdictions, this covers vérification de personne politiquement exposée (PPE); in German-speaking jurisdictions, it maps to PEP-Prüfung für KYC/AML-Compliance-Prüfungen.
Q.01
Q.02
Q.03
Q.04
Q.05
Q.06
Q.07
Q.08