Reference Integration Architecture

Most integrations follow this standard architecture.

Architecture Principles

• Persist markaazId after successful matches; reuse it for enrichment and future re‑verification.
• Avoid repeated matching over short time spans for the same entity (cache by markaazId).
• Execute enrichment APIs in a workflow along with Advanced Match or Search when possible to reduce latency.
• Log traceId for troubleshooting and include it in support requests.
  Use a decision engine to automate onboarding, risk, or routing rules.

Core Integration Workflows

Below are examples of representative Advanced Match and Search workflows. Which pattern you use will depend on whether or not you have structured business data for the API request.

Workflow 1 — Business Verification (Onboarding / KYB / Vendor)

Notes:

• End workflows on a 207 (no match) response. Only call Verification APIs after a successful Advanced Match (200) that yields a markaazId; calling without markaazId will return a 400 error for a missing required field.

Workflow 2 — Business Pre‑fill / Assisted Onboarding (Self‑Serve UI)

Notes:

• Search requests can leverage minimal request fields; include country when possible to improve results.