dapp

brickken dapp calls Dapp API JSON endpoints with the configured API key. Use brickken tx for Dapp transaction methods that follow the prepare/sign/send flow.

export BRICKKEN_API_KEY=...

dapp get

Call a Dapp API GET endpoint. The path must be relative to the configured Brickken base URL.

brickken dapp get \
  --path /get-token-info \
  --query tokenSymbol=EXMPL \
  --json

For several query parameters, repeat --query:

brickken dapp get \
  --path /get-stos \
  --query tokenSymbol=EXMPL \
  --query page=1 \
  --query limit=20 \
  --json

You can also load query parameters from a JSON or YAML file:

{
  "tokenSymbol": "EXMPL",
  "page": 1,
  "limit": 20
}

brickken dapp get --path /get-stos --file query.json --json

dapp request

Call a Dapp API JSON POST or PATCH endpoint with a request body loaded from a JSON or YAML file:

brickken dapp request \
  --method POST \
  --path /some-dapp-endpoint \
  --file request.json \
  --json

The command sends x-api-key and does not create an x402 payment. The operation is charged against the API key’s credits. Multipart file uploads such as /patch-token-docs are not supported by this JSON command. Use the REST API directly for multipart requests. Dapp tokenization, STO, and security-token methods use brickken tx prepare:

brickken tx prepare \
  --method newTokenization \
  --file new-tokenization.json \
  --json

The transaction payload must include a whitelisted signerAddress and the API key must have sufficient credits. See the raw transaction reference for the method list and client-controlled signing flow.

Getting Started

Commands

Guides

dapp get

dapp request

​dapp get

​dapp request

​Related transaction flow

dapp get

dapp request

Related transaction flow