curl --request PATCH \
--url https://api.enterprise.sandbox.uphold.com/core/kyc/processes/email \
--header 'Authorization: Bearer <token>' \
--header 'Content-Type: application/json' \
--data '
{
"input": {
"email": "john.doe@uphold.com"
}
}
'{
"email": {
"code": "email",
"status": "pending",
"verification": {
"model": "partner-verified",
"method": "manual",
"dependencies": []
},
"input": {
"email": "john.doe@uphold.com"
}
}
}KYC
Update email
Update the email process for an individual user.
PATCH
/
core
/
kyc
/
processes
/
email
curl --request PATCH \
--url https://api.enterprise.sandbox.uphold.com/core/kyc/processes/email \
--header 'Authorization: Bearer <token>' \
--header 'Content-Type: application/json' \
--data '
{
"input": {
"email": "john.doe@uphold.com"
}
}
'{
"email": {
"code": "email",
"status": "pending",
"verification": {
"model": "partner-verified",
"method": "manual",
"dependencies": []
},
"input": {
"email": "john.doe@uphold.com"
}
}
}
Update email is the endpoint through which the user registers their email address.
Submitting
input on its own registers the email as unverified (pending). Include output.verifiedAt to mark it ok immediately, or submit it in a later call to verify an existing pending registration. See verification models for details.Authorizations
OAuth 2.0 authentication.
Body
application/json
Was this page helpful?