Are you an LLM? Read llms.txt for a summary of the docs, or llms-full.txt for the full context.
Skip to content

accessCodeStatus

Whether an access code is required on this channel, and whether the account is activated.

Read required first: when it is false the channel is open and the whole code flow can be skipped. When it is true, activated says whether this account already has access — false means approveAgent and order placement will be rejected until a code is bound.

activated is the same decision POST /exchange enforces, so it does not drift from what trading will actually do.

POST/account-statustype accessCodeStatus

Decide whether to show an access-code prompt before approveAgent.

Not this?
Request body
typestringrequired

Must be `accessCodeStatus`.

"accessCodeStatus"
userstring · addressrequired

Account to query. Must be a valid EVM address — a malformed value is rejected with `400` rather than answered, so a typo cannot read as a permissive result.

channelinteger · uint32optional

Sub-exchange to evaluate against. Defaults to `0` (the main TxFlow exchange). `1` is the Outcome (prediction market) sub-exchange. A channel that is not configured is refused rather than defaulted — `eligible` is `false` with reason `Unknown channel`.

Request example
curl -X POST https://rpc.txflow-testnet.xyz/account-status \
  -H "Content-Type: application/json" \
  -H "x-api-version: 2026-08-16" \
  -d '{
  "type": "accessCodeStatus",
  "user": "0x0000000000000000000000000000000000000001"
}'
Try it
POST https://rpc.txflow-testnet.xyz/account-status
Response · AccessCodeStatusResponse 200
codeinteger

`0` on success.

dataAccessCodeStatusResponse
activatedboolean

Whether this account is activated on this channel — it holds a code, has one mid-bind, or is otherwise exempt. This is the same decision `POST /exchange` enforces, so `false` here means orders will be rejected.

channelinteger · uint32
requiredboolean

Whether an access code is needed to trade on this channel. `false` means the channel is open to everyone and the whole code flow can be skipped.

userstring · address

Echo of the requested address, lowercased.

successboolean

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

Response example
{
  "success": true,
  "code": 0,
  "data": {
    "user": "0x0000000000000000000000000000000000000001",
    "channel": 0,
    "required": true,
    "activated": false
  }
}

Next steps

Check the account itself with accountStatus.