Skip to main content
PUT
Update a previously submitted KYC or KYB record. Use this endpoint when a customer needs to correct information or provide additional documents — typically after a rejection. Only include fields you want to change.
Include an Idempotency-Key header on every request. Supply customer_id and type, then any fields you want to update. Fields not included are left unchanged.

Request body

All other fields from the original submission schema can be included to update their values. See Submit Individual KYC or Submit Business KYC for the full field reference.

Authorizations

X-Api-Key
string
header
required

Your API key (yativo_pk_...) from Developers → API Keys. Send together with X-Api-Secret.

X-Api-Secret
string
header
required

Your API secret (yativo_sk_...), shown once when the key is created.

Headers

Idempotency-Key
string
required

A unique string per request to ensure idempotent processing.

Body

application/json
customer_id
string<uuid>
required

The UUID of the customer whose KYC you are updating.

type
enum<string>
required

"individual" or "business" — must match the original submission type.

Available options:
individual,
business

Response

KYC submission updated

status
string
status_code
integer
message
string
data
object