eKYC Platform API

eKYC Platform bundles the full eKYC process — document verification and selfie/liveness verification — into a single, configurable journey selected via flow_id. Because the journey (which steps run, in what order, against which checks) is pre-configured per client, integrating against it is typically faster than integrating against the eKYC Core API, which requires you to orchestrate each check yourself.

This section documents:

  • Platform API — drive the eKYC journey directly over HTTP (Initialize → Verify ID → Verify selfie, or the bundled Onboard call) without a WebView or mobile SDK. Authenticates with the encrypted_token you generate, and the access_token Initialize returns.
  • Service API — JWT-authenticated backend endpoints for pulling application results and files, and for running supporting checks (face indexing, image upload, full verification). Authenticates with a Bearer JWT from its own Log in call.

Each surface lists its endpoints on its own Overview. The two authenticate differently, which is the main thing to get right before you start.

See also Authentication, Flow Id Reference, and SDK Integration.