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

Request Fields

Send the request as application/json.

FieldTypeRequiredValidation
transaction_idstringYes1–255 characters; letters, digits, hyphens, and underscores only. Must identify the request in your system.
nikstringYesExactly 16 digits and must begin with a digit from 1–9. Preserve it as a string.
selfiestringYesRaw Base64-encoded JPEG, JPG, or PNG image. Do not include a data-URI prefix. The decoded image must remain within the upload limit configured for your integration.
channelstringYes1–100 characters; letters, digits, and hyphens only.

Example

Code
{ "transaction_id": "insights-request-001", "nik": "3173050101900001", "selfie": "/9j/4AAQSkZJRgABAQAAAQABAAD...", "channel": "web" }

Selfie preparation

  • Use JPEG, JPG, or PNG content.
  • Base64-encode the image bytes without a data:image/...;base64, prefix.
  • Do not send an empty or truncated image.
  • Keep the decoded file within the upload limit assigned to your integration.

Insights API v1 validates the Base64 data, decoded file size, and detected image type. It does not apply a documented pixel-dimension requirement.

Last modified on October 23, 2026
AuthenticationScoring Results
On this page
  • Example
  • Selfie preparation
JSON