List RFIs

Submits or resubmits the customer's entity KYC to the provider. The first submission creates the customer at the provider. The request is `multipart/form-data`. The `data` part is the JSON data. Each other part is one file, and its part name equals a `documents[].clientFileId`. File parts and `clientFileId` values must match one to one. - If the provider already accepted a submission (`SUBMITTED` or `APPROVED`), the current status is returned. No data is written and there is no `submittedAt`. - `Idempotency-Key` is required. It links the request for audit. After a timeout, retry with the same data and the original key. - Depending on the number of files, the request can take more than 30 seconds. Set the client timeout to at least 60 seconds. - Stabo runs only the minimum checks to build the provider request and keep it safe: required fields are not empty, `data` has no unknown fields, `personId` and `clientFileId` do not repeat, file parts match, one file is at most 2 MB, and the file header is PDF, PNG, or JPEG. - The provider decides field formats, values, the number of persons per role, required files, and other rules. A failure returns `openapi.channel.rejected`. Lengths and values in the field descriptions are provider rules, checked by the provider. For a full example, see [Provider KYC and account opening](/en/docs/guide/provider-kyc#submit-kyb).