05-Search-VASP-by-Wallet-Result

This API retrieves the result of a previous 'Search VASP by Wallet Request'.

❗️This search targets only the user wallets(capable of receiving deposits) associated with VASPs. It does not include the cold wallets of VASPs.

❗️This API works in a synchronous manner, providing an immediate response upon request.

Endpoint

GET /v2/code/VerifyAddress/{requestId}

Request Parameters

Headers

Name	Type	Required	Description
X-Code-Req-Datetime	string	Required	ISO8601 UTC datetime
X-Code-Req-Nonce	string	Required	Random nonce
X-Code-Req-PubKey	string	Required	Your Public Key
X-Code-Req-Signature	string	Required	Signature
X-Request-Origin	string	Required	`code:{yourVaspEntityId}`
accept	string	Optional	`application/json`

Path Parameters

Name	Type	Required	Description
requestId	string	Required	`requestId` sent when requesting a 'Search VASP by Wallet'.

Response

Fields

Name	Type	Description
result	string	Result of the search (`valid` or `invalid`).
reasonType	string	Reason if invalid (e.g., `NOT_FOUND_ADDRESS`).
reasonMsg	string	Detailed message if invalid.
beneficiaryVaspEntityId	string	VASP's `entityId` identified in the search results.
requestId	string	`requestId` used during the request.
analysisResult	array	Array of search results from individual VASPs.

result: This is the request result.

-valid: When the wallet search results are returned successfully.

-invalid: When the wallet search result is invalid. The detailed information can be distinguished by the reasonType value.

reasonType: If the response is invalid, it explains the reason.

-NOT_FOUND_ADDRESS: When the virtual asset address cannot be found.

-LACK_OF_INFORMATION: When the requestId cannot be found.

-PROCESSING: The search has not been completed. Please wait and then request again. More than 10 seconds intervals are recommended.

-ALLIANCE_DATA_NON_UNIQUE_RESULT: Received 'valid' responses from two or more VASPs.

reasonMsg: Defines a detailed message in case of invalidity.

beneficiaryVaspEntityId: VASP's 'entityId' identified in the search results.

requestId: 'requestId' used during the request.

analysisResult: The details of the search results are as follows. The response comes as an array of objects in the form below.

analysisResult object fields:

Name	Type	Description
entityId	string	Entity ID of the searched VASP.
result	string	Search result (`NOT_FOUND_ADDRESS`, `FOUND`, `SYSTEM_NOT_AVAILABLE`).

Examples

Request

curl --request GET \
     --url https://trapi-dev.codevasp.com/v2/code/VerifyAddress/fafd59e2-aff7-4cff-b7d8-9caa0cda70da \
     --header 'X-Code-Req-Datetime: 2024-03-04T15:10Z' \
     --header 'X-Code-Req-Nonce: 989166249' \
     --header 'X-Code-Req-PubKey: YourPubkey' \
     --header 'X-Code-Req-Signature: Signature' \
     --header 'X-Request-Origin: code:yourVaspEntityId' \
     --header 'accept: application/json'

Response

{
  "result": "valid",
  "beneficiaryVaspEntityId": "example-vasp",
  "requestId": "fafd59e2-aff7-4cff-b7d8-9caa0cda70da",
  "analysisResult": [
    {
      "entityId": "bithumb",
      "result": "NOT_FOUND_ADDRESS"
    },
    {
      "entityId": "coinone",
      "result": "NOT_FOUND_ADDRESS"
    },
    {
      "entityId": "example-vasp",
      "result": "FOUND"
    }
  ]
}

On this page