Returns a list of metadata of a media file associated with a specific verification session
When to use this endpoint
- Use this endpoint to retrieve metadata (e.g., file type, size, download URL, context) about a media file uploaded during a verification session
- This endpoint returns information about the media file, not the file itself
- Common use cases include:
- Checking what media files were uploaded during verification
- Obtaining download URLs for media files
- Identifying media file types and contexts before downloading
- Reviewing media file metadata for quality assessment
- Determining which media files to download for record-keeping
Response data
Returns a list of media objects associated with the specific
sessionId. The list contains two arrays:images: Array of image metadata objects (document photos, selfies, proof of address)videos: Array of video metadata objects (video verification recordings)
Each media object includes:
- Unique identifier (
id) and download URL (url) - File metadata:
size(bytes),mimetype,context - Session relationship (
sessionId) - For videos:
durationin seconds
- Unique identifier (
The media objects are sorted based on their accuracy (e.g., does an image match the required image type) and quality. The order is determined by the automation system.
The
contextfield indicates what the media file contains (e.g.,document-front,face,address-front). The-presuffix indicates preliminary/first capture, while no suffix indicates final capture. See the Context types (image, video) documentation for additional info about the values ofimages.context.
Implementation notes
- This endpoint returns metadata about media files, not the media files themselves
- Use the
idfield from the responses (images.idorvideos.id) to download actual media files via GET /v1/media/ - The request returns media metadata from the most recent attempt only. To get a specific attempt's media metadata:
- Call GET /v1/sessions//attempts
to get the list of
attemptIdvalues - Use GET /v1/attempts//media to get the metadata of the media in that specific attempt
- Call GET /v1/sessions//attempts
to get the list of
- Empty arrays (
images: []orvideos: []) indicate no media of that type was uploaded - The deprecated
timestampfield always returnsnulland should not be used - In test integrations, it is expected behaviour that no video is returned
- This endpoint requires session-level HMAC signature authentication
- Always ensure that you use the correct API URL to send requests. See the API URL section for more info
- The order of parameters in the real API response can differ from the order you see in this documentation. This is expected and part of the Backwards compatible changes requirements
Your integration's API key (occasionally referred to as the "Token", "API public key" or "Publishable key"). Required for all API requests.
You can find your API key in the Veriff Customer Portal > Settings > API keys.
Session id signed with the shared secret key. Required to authenticate the request sender.
Verification session ID.
Session media metadata retrieved successfully
Standard identity verification with document
{
"status": "success",
"images": [
{
"id": "d69a07cf-4434-4d36-be6c-d22af7dc01fb",
"name": "document-front",
"context": "document-front",
"timestamp": null,
"size": 245678,
"mimetype": "image/jpeg",
"url": "https://exampleURL.com/v1/media/d69a07cf-4434-4d36-be6c-d22af7dc01fb",
"sessionId": "f04bdb47-d3be-4b28-b028-a652feb060b5"
}
],
"videos": []
}Proof of address verification with utility bill
{
"status": "success",
"images": [
{
"id": "a1b2c3d4-e5f6-4a5b-8c9d-e0f1a2b3c4d5",
"name": "address-front",
"context": "address-front",
"timestamp": null,
"size": 312456,
"mimetype": "image/jpeg",
"url": "https://exampleURL.com/v1/media/a1b2c3d4-e5f6-4a5b-8c9d-e0f1a2b3c4d5",
"sessionId": "f04bdb47-d3be-4b28-b028-a652feb060b5"
}
],
"videos": []
}Video verification with selfie video
{
"status": "success",
"videos": [
{
"id": "f5g6h7i8-j9k0-4l1m-9n2o-p3q4r5s6t7u8",
"name": "selfid_video",
"context": "selfid_video",
"timestamp": null,
"size": 4567890,
"mimetype": "video/mp4",
"url": "https://exampleURL.com/v1/media/f5g6h7i8-j9k0-4l1m-9n2o-p3q4r5s6t7u8",
"sessionId": "f04bdb47-d3be-4b28-b028-a652feb060b5",
"duration": 8
}
]
}Session with no media uploaded yet
{
"status": "success",
"images": [],
"videos": []
}API request status
Array of image metadata objects. Contains information about the image uploaded to the session, from the most recent attempt.
UUID v4 which identifies the uploaded media.
Name which identifies the uploaded media.
Context type of the uploaded media.
See Context types article for more info.
Always returns None/null.
Size of the uploaded media, in bytes.
File type of the uploaded media.
See Media file mimetypes article for more info.
Download URL of the media.
UUID v4 of the verification session the uploaded media belongs to.
Array of video metadata objects. Contains information about the video uploaded to the session, from the most recent attempt.
Metadata object describing a video file uploaded during verification.
UUID v4 which identifies the uploaded media.
Use with GET /v1/media/ to download the actual file.
Name which identifies the uploaded media.
Context type of the uploaded media.
See Context types article for more info.
Always returns null.
Size of the uploaded media, in bytes.
File type of the uploaded media.
Download URL for the actual media file.
UUID v4 of the verification session the uploaded media belongs to.
Duration of the uploaded media, in seconds.
Bad request
{
"status": "fail",
"code": "1101",
"message": "Validation failed"
}Unauthorized
{
"status": "fail",
"code": "1101",
"message": "Mandatory X-AUTH-CLIENT header containing the API key is missing from the request."
}Session not found
{
"status": "fail",
"code": "1101",
"message": "Resource not found"
}Internal server error
{
"status": "fail",
"code": "1101",
"message": "Something went wrong"
}Changelog
Date | Description |
|---|---|
Mar 9, 2026 | Documentation updated: parent categories rearranged, intro section expanded, request and response examples added |
Oct 2, 2025 |
|
Aug 6, 2025 | Response headers added |
May 2, 2025 |
|
Mar 12, 2025 | Documentation published |