---
title: Get Selfie
description: Ambil selfie yang diambil selama proses Human Token — tersedia selama 24 jam setelah proses selesai.
canonical: https://developer.unico.io/id/human-token/api-reference/get-selfie
locale: id
generated_by: markdown-export
---

- [/id/](/id/)
- Referensi API
- Get Selfie

**Di halaman iniGet SelfieGETAmbil selfie yang diambil selama proses Human Token.

Mengembalikan selfie biometrik yang diambil oleh pengguna selama proses Human Token. Gambar dikembalikan sebagai string yang dienkode base64.
Tersedia untuk setiap proses yang selesai dan telah melakukan pengambilan biometrik — kelima alur Human Token (`api+humantoken`, `api+liveness+humantoken`, `api+liveness+humantoken+revalidation`, `humantoken`, `humantoken+revalidation`). Tidak tersedia jika proses selesai tanpa pengambilan biometrik, karena tidak ada selfie untuk dikembalikan.
peringatanSelfie tersedia selama **24 jam** setelah proses selesai. Setelah itu, gambar dihapus secara permanen dan endpoint ini mengembalikan `404`.
### Endpoint​

LingkunganURL**Produksi**`GET https://humantoken.unico.app/client/v1/process/{processId}/selfie`
### Permintaan​

Headers
HeaderNilai`x-unico-accesskey``<your_access_key>` (lihat [Autentikasi](/id/human-token/get-started/authentication))
Parameter path
ParameterTipeWajibDeskripsi`processId`string (UUID)yaPengenal proses yang dikembalikan oleh [Buat Proses](/id/human-token/api-reference/post-processes).
### Contoh​

cURLNode.js```
curl -X GET https://humantoken.unico.app/client/v1/process/$PROCESS_ID/selfie \  -H "x-unico-accesskey: $UNICO_ACCESS_KEY"
```

```
import fetch from 'node-fetch';const res = await fetch(  `https://humantoken.unico.app/client/v1/process/${processId}/selfie`,  { headers: { 'x-unico-accesskey': process.env.UNICO_ACCESS_KEY } });const { fileContents, contentType } = await res.json();// fileContents is a base64-encoded image string
```

### Respons​

200 OK
```
{  "fileContents": "/9j/4AAQSkZJR...",  "contentType": "image/jpeg"}
```

FieldTipeDeskripsi`fileContents`string (base64)Selfie yang diambil, dienkode base64.`contentType`stringTipe MIME gambar — `image/jpeg` atau `image/png`.
### Kode Error​

400 Bad Request401 Unauthorized403 Forbidden404 Not Found429 Too Many RequestsParameter path `processId` tidak ada atau formatnya salah.Access key tidak ada atau tidak valid di header `x-unico-accesskey`. Lihat [Autentikasi](/id/human-token/get-started/authentication).Izin tidak mencukupi untuk mengakses selfie proses ini.Proses tidak ditemukan, proses selesai tanpa pengambilan biometrik, atau jendela retensi 24 jam telah berakhir.Rate limit reached. When your system receives an HTTP 429 error, you must implement mechanisms to prevent cascading failures and avoid worsening the restriction.
**Best practices:**

**Cool-down period (backoff):** Immediately halt or throttle subsequent requests from your system. Do not continuously retry failed requests in a tight loop.
**Queueing & throttling:** Buffer or queue outgoing requests on your end to control the traffic flow before re-sending them.
**Exponential backoff with jitter:** When retrying, increase the waiting time exponentially between attempts (e.g., 1 s, 2 s, 4 s, 8 s) and add a small random delay ("jitter") to prevent a herd effect where all queued requests retry at the exact same millisecond.

peringatanContinuously hitting a rate-limited endpoint without backing off can **prolong the restriction period** and severely impact your system's operational throughput. Properly throttling requests on your side ensures a smoother, more resilient integration.
For default limits, increase requests and additional details, see [Rate Limits](/id/developers/start/rate-limits).
### Selanjutnya​

Untuk hasil proses lengkap, lihat [Dapatkan Proses](/id/human-token/api-reference/get-process).
Kembali ke [Buat Proses](/id/human-token/api-reference/post-processes) untuk mengirim selfie baru.
Terakhir diperbarui pada 22 Okt 2026**