Link Verified Identity

Links the authenticated client to an existing verified identity by matching the email set on the client record. Use this when a user has multiple Steam accounts — one document scan covers all of them. Authentication: Client Token (Authorization header)

Request

No body. The identity is looked up automatically by the client’s email address (set during POST /client/verification/start).

POST https://api.assetpay.gg/client/verification/link
Authorization: CLIENT_TOKEN

Requirements

The client must have an email set on their account (provided during /start).
A verified identity with a matching email must exist (case-insensitive).
The identity must not be banned.
The identity must not have reached its maximum linked account limit (default 10).

On success, the client’s verificationLevel is immediately set to 1.

Response

{
  "requestId": "...",
  "success": true,
  "data": {
    "linked": true
  }
}

Trust Cascade

Linking is also a security mechanism. If any linked account triggers a deposit reversal, the trust factor is destroyed on every account tied to the same identity. This is by design — it’s what makes raising instant credit caps safe.

Errors

Code	Key	When
2301	`VERIFICATION_ALREADY_VERIFIED`	Client is already at level 1
2103	`CLIENT_USER_NOT_FOUND`	No `ClientUser` record exists for this Steam ID yet
2305	`VERIFICATION_ACCOUNT_CAP_REACHED`	Identity has reached its max-linked-accounts limit
2306	`VERIFICATION_ALREADY_LINKED`	Client is already linked to an identity
2310	`VERIFICATION_EMAIL_REQUIRED`	No email on the client — pass one in `/start` first
2312	`VERIFICATION_LINK_FAILED`	No verified identity matches the email, or the matched identity is banned
1102	`INVALID_TOKEN`	Client token is invalid or expired

Overview

Authentication

Client

Trading

Secure

Verification

Link Verified Identity

Request

Requirements

Response

Trust Cascade

Errors

​Request

​Requirements

​Response

​Trust Cascade

​Errors

Request

Requirements

Response

Trust Cascade

Errors