Check and build a Solana ATA

Check whether a Solana associated token account exists and build its creation transaction when needed.

POST /api/v4/dexbuilder/withdraw/ata/check-and-build

Check and build a Solana ATA

cURL

curl --request POST \
  --url https://api.dexbuilder.com/api/v4/dexbuilder/withdraw/ata/check-and-build \
  --header 'Content-Type: application/json' \
  --header 'KEY: <api-key>' \
  --header 'SIGN: <api-key>' \
  --header 'Timestamp: <api-key>' \
  --header 'X-User-Wallet-Address: <x-user-wallet-address>' \
  --data '
{
  "payer_address": "<string>",
  "target_address": "<string>"
}
'

200

Example

{
  "code": 0,
  "message": "success",
  "reason": "<string>",
  "trace_id": "<string>",
  "data": {
    "status": 123,
    "tx_data": "<string>"
  }
}

Check whether a Solana associated token account exists and build its creation transaction when needed.

Use a Broker API Key and pass the target user’s wallet in X-User-Wallet-Address. The gateway checks that the wallet belongs to your Broker. See Broker API Key and signing.

​

Usage notes

• This endpoint requires a Solana wallet in X-User-Wallet-Address; do not pass an EVM 0x address. payer_address is the user’s bound Solana wallet and pays onchain rent and fees; target_address is the ATA owner.
• When status=0, sign and broadcast the returned base64 tx_data before withdrawing. When status=1, the ATA already exists and tx_data is empty. Requery after a failed broadcast.

Authorizations

KEY · string · header · required

Broker API Key

Timestamp · string · header · required

Unix timestamp in seconds

SIGN · string · header · required

Hexadecimal HMAC-SHA512 signature generated with the Broker Secret Key

Headers

X-User-Wallet-Address · string · required

Target user's wallet address. The gateway verifies that the user belongs to the current Broker.

Body

application/json

payer_address · string · required

Bound Solana user wallet in base58

target_address · string · required

Owner address of the ATA to check, in base58

Response

200

application/json

Successful

code · integer

Business code; 0 indicates success

Example:

0

message · string

Human-readable message; success responses use success

Example:

"success"

reason · string

Error reason identifier; usually empty on success

trace_id · string

Trace ID to provide when requesting support

data · object

Show child attributes