Skip to main content
GET
/
api
/
kyc
/
face-match
/
verifications
/
{id}
/
document-image
Get Face Match images
curl --request GET \
  --url http://api.gu1.ai/api/kyc/face-match/verifications/{id}/document-image \
  --header 'Authorization: Bearer <token>'

​
Overview

After a successful Face Match request, you can download the document and selfie that were submitted by calling the two GET endpoints below. Use the same verificationId (UUID) returned in the POST response (or the id from GET verification). Use the same Authorization: Bearer API key and read KYC permission as for other Face Match routes. If a copy of an image was not kept for that verification, the corresponding endpoint returns 404 (for example when storage failed during the run).

​
Endpoints

​
Document image

GET https://api.gu1.ai/api/kyc/face-match/verifications/{verificationId}/document-image

​
Selfie image

GET https://api.gu1.ai/api/kyc/face-match/verifications/{verificationId}/selfie-image

​
Path parameters

​
verificationId
string
required
UUID of the Face Match verification (same as verificationId from POST or id from GET one/list).

​
Headers

  • Authorization: Bearer YOUR_API_KEY (required)
Include X-Organization-Id if your account is organization-scoped.

​
Responses

HTTPDescription
200Raw image bytes (Content-Type e.g. image/jpeg, image/png).
404Verification not found, not in your organization, or that image is not available for download.

​
Examples

# Document (reference image sent in POST)
curl -sS -o document.jpg \
  -H "Authorization: Bearer YOUR_API_KEY" \
  "https://api.gu1.ai/api/kyc/face-match/verifications/VERIFICATION_UUID/document-image"

# Selfie
curl -sS -o selfie.jpg \
  -H "Authorization: Bearer YOUR_API_KEY" \
  "https://api.gu1.ai/api/kyc/face-match/verifications/VERIFICATION_UUID/selfie-image"