# Submit signed wallet verification

After signing the verification message, submit the signature to have the self-custody wallet registered as a verified external wallet for management operations.

If the message the owner signed was not the exact message from the verification response, you must also provide the exact message in the request body. It should be the non-hex string used in the personal_sign request.

Endpoint: POST /account/wallets/{address}/verification
Version: 3.0.0
Security: bearer

## Path parameters:

  - `address` (string, required)

## Request fields (application/json):

  - `message` (string)

  - `signature` (string, required)

## Response 201 fields (application/json):

  - `@type` (string, required)
    Enum: "unstoppabledomains.com/partner.v3.WalletVerificationResult"

  - `operation` (object, required)

  - `operation.id` (string, required)
    Example: "op-4abb409c-9283-4589-bd36-d27a757a2165"

  - `operation.status` (string, required)
    Enum: "QUEUED", "SIGNATURE_REQUIRED", "PROCESSING", "COMPLETED", "FAILED", "CANCELLED"

  - `operation.type` (string, required)
    Enum: "DOMAIN_CLAIM", "DOMAIN_UPDATE", "DOMAIN_RETURN", "WALLET_CREATE", "WALLET_UPDATE", "WALLET_VERIFY", "ACCOUNT_UPDATE"

  - `operation.domain` (string)

  - `operation.lastUpdatedTimestamp` (number, required)
    Example: 1684356429790

  - `operation.dependencies` (array, required)