`accountAccessStatus`

Query the referral code bound to a specified main account and its trading access on a channel.

The current implementation is a public query: no signature or Token is required. Web clients may query any valid address. user is required and must be a valid EVM main account address; Agent addresses are not automatically converted to main accounts. type is case-sensitive.

Request headers

Content-Type: application/json
x-api-version: 2026-08-16
x-channel: 0

x-channel selects the channel whose trading access is queried and defaults to 0 when omitted. The examples and Try it below use that default channel.

POST/infotype accountAccessStatus

Query a main account’s bound referral code and trading access on a channel.

Request body

typestringrequired

Must be `accountAccessStatus` (case-sensitive).

"accountAccessStatus"

userstring · addressrequired

Required valid EVM main account address. Agent addresses are not automatically resolved to their main accounts.

Request example

curl -X POST https://rpc.txflow-testnet.xyz/info \
  -H "Content-Type: application/json" \
  -H "x-api-version: 2026-08-16" \
  -d '{
  "type": "accountAccessStatus",
  "user": "0xabcdef0000000000000000000000000000000001"
}'

Try it

POST https://rpc.txflow-testnet.xyz/info

Response 200

codeinteger

`0` on success.

dataobject

allowExchangeboolean

Trading access on the requested channel. Does not guarantee that an order passes all validations.

rcstring

Bound referral code; an empty string when unbound. This is not an access code.

reasonstringnullable

`null` when allowed; otherwise `Trading access unavailable`.

userstring

Queried main account address, normalized to lowercase.

successboolean

`false` on error, with `code` set and the text in `message` instead of `data`.

Response example

{
  "success": true,
  "code": 0,
  "data": {
    "user": "0xabcdef0000000000000000000000000000000001",
    "rc": "REF123",
    "allowExchange": true,
    "reason": null
  }
}

rc is a referral code, not an access code. When no referral code is bound, it is "". The returned user is lowercase.

allowExchange describes trading access for the requested channel; it does not guarantee that an order passes all validations. reason is null when access is allowed and "Trading access unavailable" otherwise.

Errors

HTTP	Scenario	message
400	Invalid address, missing `user`, or incorrect capitalization of the type	`accountAccessStatus requires a valid user address and exact type`
503	Downstream service failure or unexpected response	`Access status temporarily unavailable`

With the version header above, errors use this envelope (503 example):

{
  "success": false,
  "code": 10000,
  "message": "Access status temporarily unavailable"
}