---
title: "Get Verification Documents"
method: POST
path: "/ivs/2.0/getVerificationDocuments"
tags: ["IVS"]
---

# Get Verification Documents

`POST /ivs/2.0/getVerificationDocuments`

Use the Get Verification Documents endpoint to retrieve metadata and status for every document associated with a specific verification journey.

## Headers

- `authorization` string
- `X-Request-Id` string

## Request body

- object
  - `customerId` string, required — ID generated by you or SoFi Tech Solutions for the top-level customer (person or business) undergoing verification. Use this to correlate this event with the specific customer record in your system. Pattern: Alphanumeric identifier Example: `789XYZ2025`
  - `entityId` string, required — ID generated by you or SoFi Tech Solutions for a specific entity within a customer. For a `Person` customer type, this maps 1-to-1 with the `customerId`. For a `Business` customer type, a single customer may have multiple entities. Use this to correlate this event with the specific entity record in your system. Pattern: Alphanumeric identifier Example: `789XYZ2025`
  - `documentVerificationId` string, required — The unique identifier for the document-verification session. Pattern: Alphanumeric identifier Example: `doc-123456`
  - `requestTs` string, date-time, required — The date and time when the document status request was initiated in <a href="ref:system-time" target="_blank">our system time</a>, formatted as an ISO 8601 string. Pattern: ISO 8601 date-time (YYYY-MM-DDTHH:MM:SS) Example: `2025-01-01T00:00:00`
  - `riskServiceId` string, required — System-generated identifier that specifies the IVS configuration strategy assigned during IVS setup. Pattern: EPRP or GCORE prefix followed by colon-separated identifiers, up to 50 characters Example: ``EPRP-test-1231231:1` or `GCORE:1:2:3``
  - `providerId` string, required — The system-generated identifier for the IVS provider. Pattern: Up to 10 digits Example: `1234567890`

## Response `200`

Successful Response

- object — Successful Response
  - `customerId` string, required — ID generated by you or SoFi Tech Solutions for the customer undergoing verification. Use this to correlate this event with the specific entity record in your system.
  - `entityId` string, required — ID generated by you or SoFi Tech Solutions for the entity undergoing verification. Use this to correlate this event back to the specific entity record in your system.
  - `documentVerificationId` string, required — Unique identifier for the document-verification session.
  - `documents` object[], required — A list of every document submitted by the customer, including metadata and file names.
    - `documentId` string, required
    - `type` string, required
    - `pages` object[], required
      - `fileName` string, required
      - `imageBase64` string, required
  - `systemTs` string, date-time, required — Date-time when the system generated this response in <a href="ref:system-time" target="_blank">our system time</a>, formatted as an ISO 8601 string.
  - `riskServiceId` string, required — System-generated identifier that specifies the IVS configuration strategy assigned during IVS setup.

## Other responses

- `400` — Bad Request
- `401` — Unauthorized
- `403` — Forbidden
- `404` — Not Found
- `409` — Conflict
- `429` — Too Many Requests
- `500` — Internal Service Error
- `503` — Service Unavailable

---

[API](https://skmtc.net/galileo-ft/apis/program-api.md) · [All operations](https://skmtc.net/galileo-ft/apis/program-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/galileo-ft/program-api/revisions/bcd728f97a18/schema)