# Retrieve KYC documents Retrieves a list of KYC documents. Endpoint: GET /kyc-documents Version: latest Security: SecretApiKey, JWT ## Query parameters: - `limit` (integer) Limits the number of collection items to be returned. - `offset` (integer) Specifies the starting point within the collection of items to be returned. - `filter` (string) Filters the collection items. This field requires a special format. Use for multiple allowed values. Use for multiple fields. For more information, see Using filter with collections. - `sort` (array) Sorts and orders the collection of items. To sort in descending order, prefix with . Multiple fields can be sorted by separating each with . - `expand` (string) Expands a request to include embedded objects within the property of the response. This field accepts a comma-separated list of objects. For more information, see Expand to include embedded objects. ## Response 401 fields (application/json): - `status` (integer) HTTP status code. - `type` (string) Problem type in the form of a [URI](https://tools.ietf.org/html/rfc3986) reference. It should provide human-readable documentation for the problem type. When this member is not present, its value is assumed to be "about:blank". - `title` (string) Short, human-readable summary of the problem type. Other than for the purposes of localization, this should not change from occurrence to occurrence of the problem. - `detail` (string) Human-readable explanation that is specific to this occurrence of the problem. - `instance` (string) URI reference that identifies the specific occurrence of the problem. It may or may not yield further information if dereferenced. ## Response 403 fields (application/json): - `status` (integer) HTTP status code. - `type` (string) Problem type in the form of a [URI](https://tools.ietf.org/html/rfc3986) reference. It should provide human-readable documentation for the problem type. When this member is not present, its value is assumed to be "about:blank". - `title` (string) Short, human-readable summary of the problem type. Other than for the purposes of localization, this should not change from occurrence to occurrence of the problem. - `detail` (string) Human-readable explanation that is specific to this occurrence of the problem. - `instance` (string) URI reference that identifies the specific occurrence of the problem. It may or may not yield further information if dereferenced.