> ## Documentation Index > Fetch the complete documentation index at: https://cobo.com/developers/llms.txt > Use this file to discover all available pages before exploring further. # Get address verification > Retrieve a single self-custody address verification record by its `verification_id`, including method-specific provenance: - `verification_method=SIGNATURE` → `signature_detail` is populated. - `verification_method=SATOSHI_TEST` → `satoshi_test_detail` carries the latest challenge state (`status`, `remaining_seconds`, `matched_txid`). Use [List address verifications](#operation/list_address_verifications) to discover `verification_id` values. Try [Cobo WaaS Skill](/v2/guides/overview/cobo-waas-skill) in your AI coding assistant (Claude Code, Cursor, etc.). Describe your needs in natural language to auto-generate production-ready SDK code and debug faster 🚀 ```python Python theme={null} import cobo_waas2 from cobo_waas2.models.address_verification_detail import AddressVerificationDetail from cobo_waas2.rest import ApiException from pprint import pprint # See configuration.py for a list of all supported configurations. configuration = cobo_waas2.Configuration( # Replace `` with your private key api_private_key="", # Select the development environment. To use the production environment, change the URL to https://api.cobo.com/v2. host="https://api.dev.cobo.com/v2", ) # Enter a context with an instance of the API client with cobo_waas2.ApiClient(configuration) as api_client: # Create an instance of the API class api_instance = cobo_waas2.TravelRuleApi(api_client) verification_id = "fb377ea5-a97a-49b4-955d-23f8fdd5177a" try: # Get address verification api_response = api_instance.get_address_verification(verification_id) print("The response of TravelRuleApi->get_address_verification:\n") pprint(api_response) except Exception as e: print( "Exception when calling TravelRuleApi->get_address_verification: %s\n" % e ) ``` ```java Java theme={null} // Import classes: import com.cobo.waas2.ApiClient; import com.cobo.waas2.ApiException; import com.cobo.waas2.Configuration; import com.cobo.waas2.Env; import com.cobo.waas2.api.TravelRuleApi; import com.cobo.waas2.model.*; public class Example { public static void main(String[] args) { ApiClient defaultClient = Configuration.getDefaultApiClient(); // Select the development environment. To use the production environment, replace `Env.DEV` with // `Env.PROD defaultClient.setEnv(Env.DEV); // Replace `` with your private key defaultClient.setPrivKey(""); TravelRuleApi apiInstance = new TravelRuleApi(); UUID verificationId = UUID.fromString("fb377ea5-a97a-49b4-955d-23f8fdd5177a"); try { AddressVerificationDetail result = apiInstance.getAddressVerification(verificationId); System.out.println(result); } catch (ApiException e) { System.err.println("Exception when calling TravelRuleApi#getAddressVerification"); System.err.println("Status code: " + e.getCode()); System.err.println("Reason: " + e.getResponseBody()); System.err.println("Response headers: " + e.getResponseHeaders()); e.printStackTrace(); } } } ``` ```go Go theme={null} package main import ( "context" "fmt" coboWaas2 "github.com/CoboGlobal/cobo-waas2-go-sdk/cobo_waas2" "github.com/CoboGlobal/cobo-waas2-go-sdk/cobo_waas2/crypto" "os" ) func main() { verificationId := "fb377ea5-a97a-49b4-955d-23f8fdd5177a" configuration := coboWaas2.NewConfiguration() // Initialize the API client apiClient := coboWaas2.NewAPIClient(configuration) ctx := context.Background() // Select the development environment. To use the production environment, replace coboWaas2.DevEnv with coboWaas2.ProdEnv ctx = context.WithValue(ctx, coboWaas2.ContextEnv, coboWaas2.DevEnv) // Replace `` with your private key ctx = context.WithValue(ctx, coboWaas2.ContextPortalSigner, crypto.Ed25519Signer{ Secret: "", }) resp, r, err := apiClient.TravelRuleAPI.GetAddressVerification(ctx, verificationId).Execute() if err != nil { fmt.Fprintf( os.Stderr, "Error when calling `TravelRuleAPI.GetAddressVerification``: %v\n", err, ) fmt.Fprintf(os.Stderr, "Full HTTP response: %v\n", r) } // response from `GetAddressVerification`: AddressVerificationDetail fmt.Fprintf(os.Stdout, "Response from `TravelRuleAPI.GetAddressVerification`: %v\n", resp) } ``` ```javascript JavaScript theme={null} const CoboWaas2 = require("@cobo/cobo-waas2"); // Initialize the API client const apiClient = CoboWaas2.ApiClient.instance; // Select the development environment. To use the production environment, replace `Env.DEV` with `Env.PROD` apiClient.setEnv(CoboWaas2.Env.DEV); // Replace `` with your private key apiClient.setPrivateKey(""); // Call the API const apiInstance = new CoboWaas2.TravelRuleApi(); const verification_id = "fb377ea5-a97a-49b4-955d-23f8fdd5177a"; apiInstance.getAddressVerification(verification_id).then( (data) => { console.log("API called successfully. Returned data: " + data); }, (error) => { console.error(error); }, ); ``` ## OpenAPI ````yaml get /travel_rule/address_verifications/{verification_id} openapi: 3.0.3 info: title: Cobo Wallet as a Service 2.0 description: > The Cobo Wallet-as-a-Service (WaaS) 2.0 API is the latest version of Cobo's WaaS API offering. It enables you to access Cobo's full suite of crypto wallet technologies with powerful and flexible access controls. By encapsulating complex security protocols and streamlining blockchain interactions, this API allows you to concentrate on your core business activities without worrying about the safety of your assets. The WaaS 2.0 API presents the following key features: - A unified API for Cobo's [all four wallet types](https://manuals.cobo.com/en/portal/introduction#an-all-in-one-wallet-platform) - Support for 80+ chains and 3000+ tokens - A comprehensive selection of webhook events - Flexible usage models for MPC Wallets, including [Organization-Controlled Wallets](https://manuals.cobo.com/en/portal/mpc-wallets/ocw/introduction) and [User-Controlled Wallets](https://manuals.cobo.com/en/portal/mpc-wallets/ucw/introduction) - Programmatic control of smart contract wallets such as Safe{Wallet} with fine-grained access controls - Seamlessly transfer funds across multiple exchanges, including Binance, OKX, Bybit, Deribit, and more For more information about the WaaS 2.0 API, see [Introduction to WaaS 2.0](https://www.cobo.com/developers/v2/guides/overview/introduction). termsOfService: https://cobo.com/waas/tos/ license: name: Apache 2.0 url: https://www.apache.org/licenses/LICENSE-2.0.html contact: name: Cobo WaaS url: https://www.cobo.com/waas email: help@cobo.com version: 1.0.0 servers: - url: https://api.dev.cobo.com/v2 description: Development environment - url: https://api.cobo.com/v2 description: Production environment security: - CoboAuth: [] tags: - name: Organizations description: Operations related to Organizations. - name: Wallets description: Operations related to all wallets. - name: Wallets - MPC Wallets description: Operations related to mpc wallet. - name: Wallets - Exchange Wallet description: Operations related to exchange wallet. - name: Wallets - Smart Contract Wallets description: Operations related to smart contract wallet. - name: Transactions description: Operations related to all transactions. - name: Developers - Webhooks description: Operations related to webhooks. - name: Stakings description: Operations related to staking. - name: OAuth description: Operations related to OAuth. - name: Developers description: Operations related to developers. - name: AddressBooks description: Operations related to address books. - name: TravelRule description: Operations related to travel rule. - name: GraphQL description: Operations related to executing GraphQL queries and mutations. - name: PrimeBroker description: Operations related to prime broker. - name: AppWorkflows description: Operations related to app workflow. - name: FeeStation description: Operations related to fee station. - name: Payment description: Operations related to payment. - name: Batch Payouts description: Operations related to batch payouts. - name: Tokenization description: Operations related to tokenization. - name: AutoSweep description: Operations related to auto sweep. - name: Compliance description: Operations related to compliance. paths: /travel_rule/address_verifications/{verification_id}: parameters: - $ref: '#/components/parameters/pathAddressVerificationIdParam' get: tags: - TravelRule summary: Get address verification description: > Retrieve a single self-custody address verification record by its `verification_id`, including method-specific provenance: - `verification_method=SIGNATURE` → `signature_detail` is populated. - `verification_method=SATOSHI_TEST` → `satoshi_test_detail` carries the latest challenge state (`status`, `remaining_seconds`, `matched_txid`). Use [List address verifications](#operation/list_address_verifications) to discover `verification_id` values. operationId: get_address_verification responses: '200': $ref: '#/components/responses/getAddressVerificationResponse' 4XX: $ref: '#/components/responses/badRequestError' 5XX: $ref: '#/components/responses/internalServerError' security: - CoboAuth: [] - OAuth2: - travel_rule.read components: parameters: pathAddressVerificationIdParam: name: verification_id in: path required: true description: The unique identifier of the address verification record. schema: type: string format: uuid example: fb377ea5-a97a-49b4-955d-23f8fdd5177a responses: getAddressVerificationResponse: description: The address verification record. content: application/json: schema: $ref: '#/components/schemas/AddressVerificationDetail' badRequestError: description: >- Bad request. Your request contains malformed syntax or invalid parameters. content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' internalServerError: description: Internal server error. content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' schemas: AddressVerificationDetail: type: object title: Address verification detail description: > Full detail of a single address verification record, including method-specific provenance. - `verification_method=SIGNATURE` → `signature_detail` is populated, `satoshi_test_detail` is `null`. - `verification_method=SATOSHI_TEST` → `satoshi_test_detail` carries the latest challenge state (`status`, `remaining_seconds`, `matched_txid`); `signature_detail` is `null`. required: - verification_id - address - chain_id - status - verification_method properties: verification_id: type: string format: uuid description: The unique identifier of this verification record. example: fb377ea5-a97a-49b4-955d-23f8fdd5177a address: type: string description: The counterparty (self-custody) wallet address being verified. example: '0x1234567890abcdef1234567890abcdef12345678' chain_id: type: string description: The chain on which this address is verified. example: ETH status: $ref: '#/components/schemas/AddressVerificationStatus' verification_method: $ref: '#/components/schemas/AddressVerificationMethod' verified_at: type: integer format: int64 nullable: true description: >- Timestamp (milliseconds) when verification completed. `null` while `status=PENDING` or `FAILED`. example: 1732523887000 satoshi_test_detail: nullable: true description: > The latest Satoshi Test challenge associated with this verification. Present only when `verification_method=SATOSHI_TEST`. allOf: - $ref: '#/components/schemas/SatoshiTestChallenge' signature_detail: nullable: true description: > Off-chain signature provenance. Present only when `verification_method=SIGNATURE`. allOf: - $ref: '#/components/schemas/SignatureDetail' ErrorResponse: type: object description: The response of a failed request. required: - error_code - error_message - error_id properties: error_code: type: integer description: >- The error code. Refer to [Error codes and status codes](https://www.cobo.com/developers/v2/api-references/error-codes) for more details. error_message: type: string description: The error description. error_id: type: string description: >- The error log ID. You can provide the error ID when submitting a ticket to help Cobo to locate the issue. example: 0b6ddf19083c4bd1a9ca01bec44b24dd AddressVerificationStatus: type: string enum: - PENDING - VERIFIED - FAILED example: VERIFIED description: > The lifecycle status of an address verification record. - `PENDING`: A Satoshi Test challenge is in progress (countdown active or awaiting confirmation). - `VERIFIED`: The address ownership has been confirmed (by signature or by a matched Satoshi Test transfer). - `FAILED`: The verification attempt did not succeed (Satoshi Test expired without match, or signature verification rejected). AddressVerificationMethod: type: string enum: - SIGNATURE - SATOSHI_TEST example: SATOSHI_TEST description: > How a self-custody address was verified. - `SIGNATURE`: Verified by off-chain wallet signature (via `Get a self-custody signature challenge` + signed message). - `SATOSHI_TEST`: Verified by an on-chain micro-deposit (via Satoshi Test challenge). SatoshiTestChallenge: type: object title: Satoshi Test challenge description: >- Full information about a Satoshi Test challenge, returned by the create and get operations. required: - challenge_id - from_address - to_address - amount - token_id - chain_id - status - remaining_seconds properties: challenge_id: type: string format: uuid description: The unique identifier of the Satoshi Test challenge. example: a1b2c3d4-e5f6-7890-abcd-ef1234567890 from_address: type: string description: >- The counterparty (self-custody) wallet address that must transfer the micro-deposit. example: '0x1234567890abcdef1234567890abcdef12345678' to_address: type: string description: >- The Cobo-generated verification address that will receive the micro-deposit. example: '0xabcdef1234567890abcdef1234567890abcdef12' amount: type: string description: > The exact amount (in the token's smallest unit) that must be transferred. The amount is unique per challenge and is used together with `to_address` to identify a matching on-chain transfer. example: '1100001000000000' token_id: type: string description: >- The ID of the token used for the micro-deposit (typically the chain's native asset). example: ETH chain_id: type: string description: The chain on which the micro-deposit is expected. example: ETH status: $ref: '#/components/schemas/SatoshiTestChallengeStatus' remaining_seconds: type: integer description: > Remaining time (in seconds) before the challenge expires. `0` when the challenge is not yet submitted or has already completed/expired. example: 10550 matched_txid: type: string nullable: true description: >- The on-chain transaction hash of the matching transfer, once matched. example: 0xabc123... started_at: type: integer format: int64 nullable: true description: >- Timestamp (milliseconds) when the challenge was submitted and the countdown started. example: 1732523887000 expires_at: type: integer format: int64 nullable: true description: >- Timestamp (milliseconds) when the challenge will expire if not matched. example: 1732534687000 SignatureDetail: type: object title: Signature verification detail description: > Details of an off-chain signature that verified a self-custody address. Returned only when `verification_method=SIGNATURE`. required: - address properties: address: type: string description: The self-custody wallet address that signed the challenge. example: '0x1234567890abcdef1234567890abcdef12345678' challenge: type: string nullable: true description: The challenge string that was signed. example: > Hi, please sign this message to confirm that you are the owner of this wallet address. - Nonce: b2860f5c9f201a81bc76f33e991c1f24 - Timestamp: 1732523887 signature: type: string nullable: true description: The wallet signature submitted by the client. example: >- 0x4355c6b7e1f3d2a09c8b7e6f5d4c3b2a1908f7e6d5c4b3a2918f7e6d5c4b3a2918f7e6d5c4b3a2918f7e6d5c4b3a2918f7e6d5c4b3a2918f7e6d5c4b3a291b verified_at: type: integer format: int64 nullable: true description: Timestamp (milliseconds) when the signature was verified. example: 1732523887000 SatoshiTestChallengeStatus: type: string enum: - PREPARE - PENDING - MATCHED - VERIFIED - EXPIRED - DELETED example: PENDING description: > The lifecycle status of a Satoshi Test challenge. - `PREPARE`: Challenge created (address and amount returned); the 180-minute countdown is not started yet. - `PENDING`: Challenge submitted; countdown active, waiting for the counterparty's on-chain transfer. - `MATCHED`: An on-chain transfer matching the expected amount has been observed; waiting for block confirmations. - `VERIFIED`: The matched transfer reached confirmation — the address is verified. - `EXPIRED`: Challenge was not matched within 180 minutes. - `DELETED`: Challenge was cancelled by the client. securitySchemes: CoboAuth: type: apiKey in: header name: BIZ-API-KEY description: > The API key. For more details, refer to [API key](https://www.cobo.com/developers/v2/guides/overview/cobo-auth#api-key). In the API playground, enter your [API secret](https://www.cobo.com/developers/v2/guides/overview/cobo-auth#api-secret), and your API key will be accordingly calculated. OAuth2: type: oauth2 description: >- The [Org Access Token](https://www.cobo.com/developers/v2/apps/org-access-tokens). Use this authorization method only if you are developing Cobo Portal Apps for installation and use across different organizations. flows: authorizationCode: authorizationUrl: https://auth.cobo.com/authorize tokenUrl: https://auth.cobo.com/oauth/token scopes: address_book.read: Read address book api_key.read: Read API key information callback.read: Read callback message callback.resend: Resend callback message wallet.create: Create wallet wallet.read: Read wallet information wallet.update: Update wallet information wallet.delete: Delete wallet information wallet.create_address: Create wallet address wallet.manage_utxo: Manage UTXO mpc_project.create: Create MPC project mpc_project.read: Read MPC project information mpc_project.update: Update MPC project information mpc_vault.create: Create MPC Vault mpc_vault.read: Read MPC Vault information mpc_vault.update: Update MPC Vault information mpc_key_group.create: Create MPC key group mpc_key_group.read: Read MPC key group information mpc_key_group.update: Update MPC key group information mpc_key_group.delete: Delete MPC key group information transaction.read: Read transaction information transaction.withdraw: Make withdrawals transaction.estimate_fee: Estimate transaction fee transaction.contract_call: Initiate contract calls transaction.message_sign: Initiate message signings transaction.stake: Stake assets transaction.unstake: Unstake assets transaction.unstake_withdraw: Withdraw unstaked assets transaction.manage: Manage ongoing transactions transaction.update: Update transaction notes travel_rule.read: Read travel rule information travel_rule.edit: Edit travel rule information webhook.read: Read webhook URLs/events webhook.edit: Edit webhook URLs webhook.resend: Resend webhook events payment_orders_payin.create: Create pay-in order payment_orders_payin.read: Read pay-in order information payment_orders_payin.update: Update pay-in order payment_orders_refund.create: Create payment refund order payment_orders_refund.read: Read payment refund order information payment_settlement.create: Create payment settlement request payment_settlement.read: Read payment settlement request information payment_merchant.create: Create payment merchant payment_merchant.read: Read payment merchant information payment_merchant.update: Update payment merchant payment_forced_sweep.create: Create payment force sweep request payment_forced_sweep.read: Read payment force sweep request information compliance_funds.refund: Refund compliance funds request compliance_funds.isolate: Isolate compliance funds request compliance_funds.unfreeze: Unfreeze compliance funds request compliance_funds.read: Read compliance funds request information compliance_kyt_review.update: Update KYT review status compliance_kyt_decisions.update: Update KYT decision status compliance_kyt_status.read: Read KYT screening status compliance_kya_screenings.create: Create KYA address screening requests compliance_kya_screenings.read: Read KYA address screening results ````