PrivyPrivy
Sign in
  • Documentation
Back to Documentation
B2B Digital Certificate Issuance Support
OverviewChangelog
Insights API
    v1
      OverviewQuickstartEnvironmentsAuthenticationRequest FieldsScoring ResultsErrors
Face Compare API
KTP OCR API
ID Card Forgery
API Explorer
powered by Zudoku
Sign in
v1

Overview

Insights API v1 accepts an individual's NIK and selfie and returns a biometric insight score for use within a digital certificate issuance workflow. It does not define a public pass threshold, make an issuance decision, or issue a digital certificate.

Endpoint

POST /api/v1/insights

How it works

  1. Send a unique transaction ID, the individual's NIK, a Base64-encoded selfie, and the originating channel.
  2. Privy validates the credentials and request fields.
  3. Privy evaluates the selfie and returns a numeric score.
  4. Use client_transaction_id and transaction_id to correlate the result with your request and Privy's processing record.

The API does not define a public pass threshold. Treat score as the insight returned by Privy and follow the interpretation agreed for your integration.

Next steps

  • Follow the Quickstart to submit a request.
  • Review Authentication for Basic and Bearer HMAC options.
  • Check Request Fields before encoding a selfie.
Last modified on October 23, 2026
ChangelogQuickstart
On this page
  • Endpoint
  • How it works
  • Next steps