---
title: "Create a Sumsub SDK token"
method: POST
path: "/api/v1/sumsub/create-access-token"
tags: ["External Wallet Access Mode"]
---

# Create a Sumsub SDK token

`POST /api/v1/sumsub/create-access-token`

Creates an access token to initialize the Sumsub SDK for KYC verification. The NFC scan step requires the Sumsub mobile SDK; it is not available in the web SDK. Omit userId unless UR gave you an explicit tenant pattern.

## Headers

- `tokenId` string, required
- `network` string, required
- `sign` string, required
- `hash` string, required
- `deadline` string, required

## Request body

- object
  - `userId` string — Optional. Server derives the Sumsub user id from Full Auth context when omitted.
  - `levelName` string — Specific Sumsub level name. Empty uses the default.
  - `ttl` integer — Token time-to-live in seconds. Default configured by the server.
  - `isRetryVerification` boolean — True for KYC retry scenarios.
  - `retryLevel` integer — Retry level (1-7); valid only when isRetryVerification is true.
  - `stepType` string — Specific verification step to reset, e.g. IDENTITY.
  - `failureReason` string — Failure reason, used for logging.

## Response `200`

Response envelope. For the user API, retCode 0 means success; for the partner API, code 0 means success. Business rejections return HTTP 200 with a non-zero code.

- EwaEnvelope — Standard response envelope for the user API (api.ur.app).
  - `retCode` integer, required — 0 on success; non-zero indicates failure.
  - `retMsg` string, required — Human-readable message; error details when retCode is non-zero.
  - `result` unknown
  - `timeNow` integer — Server timestamp in milliseconds.

---

[API](https://skmtc.net/ur/apis/ur-api.md) · [All operations](https://skmtc.net/ur/apis/ur-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/ur/ur-api/revisions/087dcf516ce2/schema)