Skip to main content
POST
/
v3
/
lists
/
{list_uuid}
/
entries
/
face-upload
curl -X POST "https://verification.didit.me/v3/lists/{list_uuid}/entries/face-upload/" \
  -H "x-api-key: YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"image": "/9j/4AAQSkZ...", "comment": "Known fraudster"}'

{
  "uuid": "a1b2c3d4-...",
  "value": "face-uuid-here",
  "display_label": "",
  "comment": "Known fraudster",
  "added_by": "api",
  "reference_session_id": null,
  "reference_session_number": null,
  "reference_object_uuid": "face-uuid-here",
  "metadata": {
    "reference_image_url": "https://..."
  },
  "created_at": "2025-06-09T12:26:54Z"
}
Upload a base64-encoded face image to a face-type blocklist. Didit extracts the biometric data, validates a face is detected, inserts the embedding into the matching database, and creates a blocklist entry. Any future verification session matching this face will be automatically declined. Only available for lists with entry_type: face.
If you’re blocklisting a face from an existing session, use Create entry with reference_session_id instead — the backend handles the biometric extraction automatically and links the entry back to the session.

​
Request body

FieldTypeRequiredDescription
imagestringYesBase64-encoded face image (JPG, PNG, or WebP)
commentstringNoComment or reason for blocklisting
curl -X POST "https://verification.didit.me/v3/lists/{list_uuid}/entries/face-upload/" \
  -H "x-api-key: YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"image": "/9j/4AAQSkZ...", "comment": "Known fraudster"}'

{
  "uuid": "a1b2c3d4-...",
  "value": "face-uuid-here",
  "display_label": "",
  "comment": "Known fraudster",
  "added_by": "api",
  "reference_session_id": null,
  "reference_session_number": null,
  "reference_object_uuid": "face-uuid-here",
  "metadata": {
    "reference_image_url": "https://..."
  },
  "created_at": "2025-06-09T12:26:54Z"
}
The image must contain a clearly visible face. If no face is detected, a 400 error is returned.