Validate crypto address

This endpoint validates a given crypto address, along with an optional destination tag if required by the blockchain network. It ensures that the address is compatible with the specified coin network and that any additional information, such as the destination tag, is accurate. This validation helps prevent errors in transactions and ensures compliance with network standards.

SecuritybearerAuth
Request
header Parameters
bp-user-id
required
string <uuid>
Example: 12312312-2be6-4522-977e-ea4d92c45e86
Request Body schema: application/json

The withdrawal offer

address
required
string

The crypto address to be validated. This is the primary address provided by the user, which needs verification against the specified coin network.

coin_network_id
required
string <uuid>

A unique identifier representing the coin and network combination. This ensures that the validation is specific to the correct blockchain network.

destination_tag
string or null

An additional identifier used by certain blockchain networks (e.g., XRP, Stellar) to direct the transaction to a specific account or purpose within the address. If the network requires a destination tag, this field is necessary.

destination_tag_type
string or null

Specifies the type of destination tag being used, which can vary by blockchain (e.g., “memo_id” for Stellar, “memo_text” for EOS). This ensures that the correct format is applied during validation.

Enum: "memo_id" "memo_text"
Responses
200

Success Response

401

Unauthorized

403

Forbidden

422

Validation Error

500

Internal Error

503

Service unavailable

post/v1/crypto-transfers/addresses/validate
Request samples
application/json
{
  • "address": "1A1zP1eP5QGefi2DMPTfTL5SLmv7DivfNa",
  • "coin_network_id": "d969468d-2be6-4522-977e-ea4d92c45e86",
  • "destination_tag": "123456789",
  • "destination_tag_type": "memo_id"
}
Response samples
application/json
{
  • "data": {
    }
}