Integration

Drop into any stack — REST API, mobile SDKs, or no-code.

Engineers ship in days, not quarters. Compliance leads can launch a verification flow without writing a line of code. One contract, every interface included.

REST API

Single endpoint, JSON in / JSON out. OpenAPI 3.1 spec, idempotency keys, rate-limit headers, automatic retry.

Mobile SDKs

Native iOS (Swift), Android (Kotlin), React Native, and Flutter packages. Five-minute drop-in screening.

Hosted Verification

Branded screening page or iframe — share a URL, embed in a portal, no front-end work required.

Visual Flow Designer

No-code drag-and-drop canvas for screening rules: branching logic, escalations, custom evidence prompts.

Webhooks & Events

Real-time push for hits, status changes, list updates, monitoring alerts. Signed payloads, automatic retries.

SSO & RBAC

SAML 2.0 / OIDC single sign-on, fine-grained roles for analysts, supervisors, MLROs and auditors.

Five steps. From auth to audit.

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
Authorise
/api/Authorization
Step 02
Screen
/api/Individual_search
Step 03
Results
matchCount · scored
Step 04
Profile
/api/View_Profile
Step 05
Case
/api/Case_detail
412 ms
Avg. latency
99.99 %
Uptime SLA
TLS 1.3
Wire encryption
JWT
Bearer auth
5 calls
End-to-end
# Step 01 — Exchange API key for a bearer token
POST https://liveexshield.ca/Kyc_RightSource_services_V3/api/Authorization
Content-Type: application/json
{
  "code":    10042,
  "apI_Key": "sk_live_••••••••••••••••••"
}

// → 200 OK · 38 ms
{
  "access_token": "eyJhbGciOiJIUzI1NiIsInR5cCI6...",
  "expires_in":   3600,
  "token_type":   "Bearer"
}
# Step 02 — Screen an individual against sanctions / PEP / watchlists
POST https://liveexshield.ca/Kyc_RightSource_services_V3/api/Individual_search
Authorization: Bearer eyJhbGciOiJIUzI1NiIsInR5cCI6...
Content-Type: application/json
{
  "name":            "A. Petrov",
  "dob":             "1972-04-18",
  "gender":          "M",
  "countries":       ["RU"],
  "datasets":        ["sanctions", "pep", "adverse-media"],
  "pepTiers":        ["L1", "L2"],
  "threshold":       75,
  "matching":        "unified",
  "dobMatching":     "flex-1y",
  "dobRequired":     true,
  "countryRequired": true
}
// → 200 OK · 412 ms · 3 candidates above threshold
{
  "results": {
    "matchCount": 3,
    "matches": [
      {
        "resourceId": "prof_8f3c1b2e...",
        "name":       "Andrei Konstantinovich Petrov",
        "score":      94,
        "tier":       "PEP-L1",
        "sources":    ["OFAC-SDN", "EU-CONS"],
        "confidence": 0.94,
        "verdict":    "escalate_l2"
      },
      { "resourceId": "prof_71ad...", "score": 76, "tier": "adverse" },
      { "resourceId": "prof_55c4...", "score": 71, "tier": "cleared" }
    ]
  }
}
# Step 04 — Pull the full profile for a chosen resourceId
POST https://liveexshield.ca/Kyc_RightSource_services_V3/api/View_Profile?resourceId=prof_8f3c1b2e...
Authorization: Bearer eyJhbGciOiJIUzI1NiIsInR5cCI6...

// → 200 OK · full 360° record
{
  "name":     "Andrei Konstantinovich Petrov",
  "aliases":  ["А. Петров", "Andriy Petrov"],
  "dob":      "1972-04-18",
  "addresses":  [{ "country": "RU", "city": "Moscow" }],
  "identifiers":[{ "type": "PASSPORT", "number": "PRS•••3471" }],
  "sanctions":[{ "list": "OFAC-SDN", "added": "2022-03-01" }],
  "pep":      { "tier": "L1", "role": "State enterprise director" },
  "linkedEntities": ["ent_4a2c...", "ent_9b71..."]
}
# Step 05 — Look up the case ID for audit / closure
POST https://liveexshield.ca/Kyc_RightSource_services_V3/api/Case_detail?Case_id=CASE-2026-04421
Authorization: Bearer eyJhbGciOiJIUzI1NiIsInR5cCI6...

// → 200 OK · case + audit trail
{
  "caseId":      "CASE-2026-04421",
  "status":      "escalated_l2",
  "assignee":    "mlro@bank.example",
  "openedAt":    "2026-05-05T09:32:11Z",
  "decisionLog": [
    { "at": "09:32", "by": "SNAP-AI",  "action": "flagged · score 94" },
    { "at": "09:34", "by": "analyst1", "action": "4-eyes review opened" },
    { "at": "10:18", "by": "mlro",     "action": "approved escalation" }
  ]
}

Need the swagger? View live OpenAPI spec →

From sandbox to production in 10–15 business days.

1
Day 1 · 1 hour

Sandbox key issued

Sign up, get a sandbox key by email, run the first screening call from cURL or Postman before the kettle boils.

2
Days 2–3

Prototype integration

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.

3
Days 4–7

Configure thresholds & rules

Co-design matching thresholds, escalation rules, four-eyes review and audit fields with our solutions team. Apply the configuration via the admin console.

4
Days 8–12

UAT & SSO wiring

Connect SSO, set up RBAC roles, run UAT against your historical book, verify webhooks fire on hits and status changes.

5
Day 13–15

Production go-live

Cut over to the production endpoint with around-the-clock support from day one. Daily monitoring delta scans start immediately.

A sandbox in your inbox in 24 hours.

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.

Talk to Sales