Empowered by
Engineers ship in days, not quarters. Compliance leads can launch a verification flow without writing a line of code. One contract, every interface included.
Single endpoint, JSON in / JSON out. OpenAPI 3.1 spec, idempotency keys, rate-limit headers, automatic retry.
Native iOS (Swift), Android (Kotlin), React Native, and Flutter packages. Five-minute drop-in screening.
Branded screening page or iframe — share a URL, embed in a portal, no front-end work required.
No-code drag-and-drop canvas for screening rules: branching logic, escalations, custom evidence prompts.
Real-time push for hits, status changes, list updates, monitoring alerts. Signed payloads, automatic retries.
SAML 2.0 / OIDC single sign-on, fine-grained roles for analysts, supervisors, MLROs and auditors.
A single sequence covers an entire compliance check: authenticate, screen the entity, inspect the matches, drill into the candidate's full profile, and look up the case state. Watch the pulse travel through every endpoint — that is one real production call.
# Step 01 — Confirm the service is up and check auth_required GET https://lexamlhelpapi.amlhlep.com/kycrs/healthz X-API-Key: "<your-key-here>" // → 200 OK · 38 ms { "status": "ok", "version": "20.0.0", "auth_required": false, "search_ready": true } # When auth_required is false the endpoint is open — your client should # still send X-API-Key so it works the moment auth is enforced.
# Step 02 — Screen an individual against PEP / SAN / RRE / POI / DD / INS POST https://lexamlhelpapi.amlhlep.com/kycrs/search/individuals X-API-Key: "<your-key-here>" Content-Type: application/json { "name": "Vladimir Putin", "datasets": ["SAN", "PEP"], "threshold": 85, "addresses": [{ "geography": "RU", "city": "Moscow" }], "dob": "1952-10-07", "dobMatching": "sameYear", "gender": "Male", "matching": "fuzzy", "transliterateName": true }
// → 200 OK · 412 ms · top hit + jurisdictional sanction body IDs { "results": { "matchCount": 1, "matches": [ { "qrCode": "116301", "resourceId": "bdaeabc844deab67d9c782d2d0a12c79bbd72b46...", "score": 100, "match": "Putin", "name": "Vladimir Vladimirovich Putin", "countries": ["RU"], "addresses": [ { "geography": "RU", "city": "Moscow" } ], "datasets": ["PEP-CURRENT", "SAN-CURRENT"], "currentSanBodyIds": [2, 8, 16, 19, 21], // OFAC, UN, EU, HMT, SECO "datesOfBirth": ["1952-10-07"], "gender": "Male" } ] } }
# Step 04 — Pull the full enriched profile by resourceId from Step 03 GET https://lexamlhelpapi.amlhlep.com/kycrs-profile/individuals/{resourceId} X-API-Key: "<your-key-here>" // → 200 OK · full enriched profile { "qrCode": "116301", "resourceId": "bdaeabc844deab67d9c782d2d0a12c79bbd72b46...", "firstName": "Vladimir", "middleName": "Vladimirovich", "lastName": "Putin", "gender": "Male", "datesOfBirthIso": ["1952-10-07"], "nationalitiesIsoCodes": ["RU"], "datasets": ["PEP-CURRENT", "SAN-CURRENT"], "aliases": [{ "aliass": "В. В. Путин", "type": "AKA" }], "addresses": [{ "city": "Moscow", "countryIsoCode": "RU" }], "sanEntries": { /* designations per body */ }, "pepEntries": { /* offices held */ }, "evidences": [/* source citations */] }
# Step 05 — Screen a legal entity (same hybrid pipeline as individuals) POST https://lexamlhelpapi.amlhlep.com/kycrs/search/businesses X-API-Key: "<your-key-here>" Content-Type: application/json { "name": "Zurich Insurance Company Ltd", "datasets": ["SAN", "PEP", "RRE"], "threshold": 85, "addresses": [{ "geography": "CH" }] } // → 200 OK · matchCount = 11 · then call /kycrs-profile/businesses/{rid} { "results": { "matchCount": 11, "matches": [ { "score": 100, "match": "Zurich Insurance Company Ltd", "name": "Zurich Insurance Company Ltd", "countries": ["DE"], "addresses": [{ "geography": "DE", "city": "Frankfurt" }], "datasets": ["PEP-LINKED"], "currentSanBodyIds": [], "resourceId": "…" } ] } }
Need the swagger? Open the full API guide → / Live OpenAPI Swagger UI inside
Sign up, get a sandbox key by email, run the first screening call from cURL or Postman before the kettle boils.
Drop in our SDK or call the REST API directly. Sample-screen 100 historical names from your book and compare side-by-side with the incumbent vendor's last results.
Co-design matching thresholds, escalation rules, four-eyes review and audit fields with our solutions team. Apply the configuration via the admin console.
Connect SSO, set up RBAC roles, run UAT against your historical book, verify webhooks fire on hits and status changes.
Cut over to the production endpoint with around-the-clock support from day one. Daily monitoring delta scans start immediately.
Tell us a bit about your stack and use case — we'll send you a sandbox API key plus a 30-minute walkthrough on the call.
