Update capability request

Corrects or adds to the request's kyb_data, and attaches documents. Never changes the status.

kyb_data is shallow-merged into what is stored — top-level keys you send overwrite or add, every other key is kept — and re-validated the way create validates it. Documents attach the same way as on create (multipart/form-data, one files_<purpose> part per document) and are appended to what that key already holds.

During pending_clarification this call alone does not return the request to review — follow it with POST /v1/requests/{id}/resubmit. See the Capability requests API guide.

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

Request ID

Body Params
kyb_data
object

Pick the shape for the request's product_code. Any files_<purpose> key beyond the ones listed is also accepted and stored verbatim (except files_draft).

Headers
string

Organization ID of a child account to act on behalf of. Requires an enabled linked-transactions relationship in which the authenticated parent FULLY MANAGES that child, and a grant covering this route. Merchant (Basic) auth only.

string
enum
Defaults to application/json

Generated from available request content types

Allowed:
Responses

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