List the documents on file for a KYB case

Returns the manifest of every document currently on file for a business entity: its own documents grouped by requirement slug, and each declared beneficial owner’s identity documents grouped by the kind of document uploaded. This is the read half of POST /ukyb/documents — the only way to discover a fileId without already holding one, since POST/PATCH /ukyb never echo one back.

Reports only the live set. Business documents accumulate — every file ever uploaded for a slug stays live, so uploading company-profile twice returns both files under it. A UBO’s identity documents replace — re-uploading a kind retires everything previously held under it, so only the newest upload for that kind appears. Either way this is the same set POST /ukyb/submit’s completeness check reads: a document visible here is a document the gate will find, and one missing here is one the gate will name as a gap.

Downloading a UBO's file. Use the beneficial owner's own entityId from the ubos[] entry — not the business entity id from the top level of this response — when calling GET /entity/{entityId}/file/{fileId}/presigned-url for one of their files. That endpoint checks the file belongs to the entity you name, and a UBO’s identity documents belong to their own INDIVIDUAL entity.

An entity that exists but has nothing uploaded yet still returns 200, with business and ubos both empty (or ubos populated with owners who have no documents yet, once a UBO set has been declared) — a case that has not uploaded anything is a fact about it, not grounds for a 404.

Recent Requests
Log in to see full request history
TimeStatusUser Agent
Retrieving recent requests…
LoadingLoading…
Path Params
uuid
required

The BUSINESS entity being onboarded.

Responses

Language
Credentials
Header
URL
LoadingLoading…
Response
Click Try It! to start a request and see the response here! Or choose an example:
application/json