Create a Sumsub access token
Partner Auth: EIP-191 signature by the partner's registered backend key, with X-Api-Deadline and optional X-Api-PublicKey headers. See the Signature and verify guide.
The user's URID. Required for this endpoint; requests without it fail with INVALID_PARAM.
Your partner-side user id. Send at least one of X-Ur-Id or X-External-User-Id.
Partner Auth EIP-191 signature over the canonical message plus the deadline.
Unix timestamp in seconds after which the signature is no longer valid.
Partner public key used to verify the signature.
Empty body by design. UR reads urId from the X-Ur-Id header and resolves the active onboarding session server-side.
Business result envelope. code 0 means success; business rejections return HTTP 200 with a non-zero code.
Business result code. 0 means success; business rejections return HTTP 200 with a non-zero code.
Human-readable diagnostic for non-zero codes.
POST /api/fma/v1/kyc/sumsub-access-token HTTP/1.1
Host: openapi.ur.app
X-Api-Signature: text
X-Ur-Id: text
X-Api-Deadline: text
X-Api-PublicKey: text
Content-Type: application/json
Accept: */*
Content-Length: 2
{}Business result envelope. code 0 means success; business rejections return HTTP 200 with a non-zero code.
{
"code": 0,
"message": "ok",
"data": {
"token": "_act-jwt-eyJhbGciOiJub25lIn0...."
}
}Last updated