---
title: "Create a Sumsub access token by network"
method: POST
path: "/v1/create-access-token-by-network"
tags: ["External Wallet Access KYC"]
---

# Create a Sumsub access token by network

`POST /v1/create-access-token-by-network`

Creates a Sumsub access token for External Wallet Access Mode users whose URID NFT lives on an external network. UR issues the token only after an on-chain ownership check: walletProvider(tokenId) on the account contract of the requested network must equal the calling partner's id. The token TTL is fixed at 20 minutes server-side.

## Headers

- `X-Api-Signature` string, required
- `X-Api-Deadline` string, required
- `X-Api-PublicKey` string, required

## Request body

- KycByNetworkRequest
  - `tokenId` string, required — URID NFT token id.
  - `network` string, required — Network or chain identifier, for example 5000 or 11155111.

## Response `200`

Business result envelope. code 0 means success; business rejections return HTTP 200 with a non-zero code.

- KycAccessTokenByNetworkResponse
  - `code` integer — Business result code. 0 means success; business rejections return HTTP 200 with a non-zero code.
  - `message` string — Human-readable diagnostic for non-zero codes.
  - `data` object
    - `token` string — Sumsub access token, usually starting with act-. Used to initialize the Sumsub SDK. This endpoint returns only the token; it does not return a Sumsub applicant id.

---

[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)