commit d555c7f61a4e44b6e41aaa454f3aa0b4e9c23cb6 parent 0b30faf82a58aabfb07be887e7441fb1ca1e43a8 Author: Christian Grothoff <christian@grothoff.org> Date: Wed, 9 Apr 2025 11:43:19 +0200 change kyc-upload to require a JSON body Diffstat:
| M | core/api-exchange.rst | | | 19 | ++++++++++++++++--- |
1 file changed, 16 insertions(+), 3 deletions(-)
diff --git a/core/api-exchange.rst b/core/api-exchange.rst @@ -5517,9 +5517,10 @@ regulatory compliance. **Request:** - Basically oriented along the possible formats of a HTTP form being - POSTed. Details will depend on the form. The server will try to decode the - uploaded body from whatever format it is provided in. + JSON body with data depending on the form being submitted. + Details will thus completely depend on the form, but it + should include a form ID and be generally of type + `ExchangeKycUploadFormRequest`. **Response:** @@ -5533,6 +5534,18 @@ regulatory compliance. :http:statuscode:`413 Request Entity Too Large`: The body is too large. + **Details:** + + .. ts:def:: ExchangeKycUploadFormRequest + + interface ExchangeKycUploadFormRequest { + + // Which form is being submitted. Further details depend on the form. + // @since protocol **v26**. + form_id: string; + } + + .. http:post:: /kyc-start/$ID The ``/kyc-start/$ID`` POST endpoint allows the SPA to set up a new external