post-kyc-upload-ID.rst (1101B)
1 .. http:post:: /kyc-upload/$ID 2 3 The ``/kyc-upload/$ID`` POST endpoint allows the SPA to upload 4 client-provided evidence. The ``$ID`` will be provided as part of the 5 ``/kyc-info`` body. This is for checks of type ``FORM``. In practice, 6 ``$ID`` will encode the ``$ACCESS_TOKEN``, legitimization measure serial ID 7 (to disambiguate) and the index of the selected measure (but these details 8 should be irrelevant for the client). 9 10 This endpoint was introduced in protocol **v20**. 11 12 **Request:** 13 14 JSON body with data depending on the form being submitted. 15 Details will thus completely depend on the form, but it 16 MUST include a form ID and be generally of type 17 `CustomerKycAttributes`. 18 19 **Response:** 20 21 :http:statuscode:`204 No Content`: 22 The information was successfully uploaded. The SPA should fetch 23 an updated ``/kyc-info/``. 24 :http:statuscode:`404 Not Found`: 25 The ``$ID`` is unknown to the exchange. 26 :http:statuscode:`409 Conflict`: 27 The upload conflicts with a previous upload. 28 :http:statuscode:`413 Request Entity Too Large`: 29 The body is too large.