get/v1/admin/applications/{id}/evidence/{filename}

Fetch one submission evidence screenshot

Operation: adminApplicationEvidence
Authentication: API key

A screenshot the submission worker took while driving a government portal.

The filenames are listed on the application detail, under each submission. **No part of a filesystem path comes from this request** — the filename selects among paths the worker already recorded, and the selected path is served only after it is confirmed to sit inside the evidence root.

These carry applicant passport data, so the read is audited and the response is `no-store`. They are kept on a retention timer: a 404 can mean the file has been swept, not that it never existed.

Request

Parameters

idpathrequiredstring

filenamepathrequiredstring

Responses

200The screenshot.

Free-form JSON object.

400The request body or query failed validation.

errorobjectrequired

401No key, an unknown key, a revoked key, or a key whose tenant is not active. All four return an identical body on purpose: distinguishing them would let a caller discover which partners we have.

errorobjectrequired

403`projects:write` is required. No partner key is ever issued this scope.

errorobjectrequired

404Not found, or not yours. A resource belonging to another tenant answers 404 rather than 403, because 403 would confirm the record exists.

errorobjectrequired

Example

curl

curl -X GET https://api.haavisa.com/v1/admin/applications/<id>/evidence/<filename> \
  -H "Authorization: Bearer $HAAVISA_API_KEY"

More in Admin

Something unclear? The eligibility guide explains the model behind the answers; the errors guide covers the envelope.