Skip to main content
Hero Light

​
Overview

The Brickken Dapp API is the API-key authenticated surface for tokenized asset workflows. Use it when your integration owns a Brickken API key and wants to prepare transactions for a wallet to sign, submit signed transactions, or read tokenization and STO data. Use the Agentic API, MCP, or CLI for private-key based agentic flows.

​
Base URLs

EnvironmentBase URL
Sandboxhttps://api.sandbox.brickken.com
Productionhttps://api.brickken.com

​
Authentication

Send your API key in every request: 
x-api-key: YOUR_BRICKKEN_API_KEY
Request a key from tech@brickken.com with the email tied to your Brickken account.

Postman Collection

Download the official Postman collection and environments to explore every endpoint with ready-to-run example requests.

​
Transaction Flow

Most write operations use the same three-step flow:
  1. Prepare unsigned transactions with POST /prepare-transactions.
  2. Sign every returned transaction with the wallet matching signerAddress.
  3. Send the signed payloads with POST /send-transactions, then poll GET /get-transaction-status.
curl --request POST 'https://api.sandbox.brickken.com/prepare-transactions' \
  --header 'Content-Type: application/json' \
  --header 'x-api-key: YOUR_BRICKKEN_API_KEY' \
  --data '{
    "chainId": "11155111",
    "method": "newTokenization",
    "tokenizerEmail": "issuer@example.com",
    "signerAddress": "0xYourWallet",
    "tokenName": "Example Asset",
    "tokenSymbol": "EXMPL",
    "tokenType": "RWA_TOKEN",
    "supplyCap": "1000000",
    "url": "https://example.com/token-docs"
  }'
The response includes txId and transactions. Sign the transaction or transactions locally, then send them: 
curl --request POST 'https://api.sandbox.brickken.com/send-transactions' \
  --header 'Content-Type: application/json' \
  --header 'x-api-key: YOUR_BRICKKEN_API_KEY' \
  --data '{
    "txId": "0xPreparedTransactionId",
    "signedTransactions": ["0xSignedRawTransaction"]
  }'

​
Write Endpoints

EndpointPurpose
POST /prepare-transactionsPrepare any supported transaction method by passing method in the JSON body.
POST /prepare-transactions/newTokenizationPrepare a new tokenized asset.
POST /prepare-transactions/mintTokenPrepare token minting.
POST /prepare-transactions/whitelistPrepare whitelist updates.
POST /prepare-transactions/burnTokenPrepare token burning.
POST /prepare-transactions/transferFromPrepare allowance-based token transfer.
POST /prepare-transactions/transferToPrepare direct token transfer.
POST /prepare-transactions/approvePrepare allowance approval.
POST /prepare-transactions/dividendDistributionPrepare dividend distribution.
POST /prepare-transactions/newStoPrepare a Security Token Offering.
POST /prepare-transactions/newInvestPrepare an STO investment.
POST /prepare-transactions/claimTokensPrepare token claims from an STO.
POST /prepare-transactions/closeOfferPrepare an STO close operation.
POST /send-transactionsSubmit signed transactions returned by prepare.
PATCH /patch-token-docsUpdate token documentation and branding files.

​
Supported Methods

Areamethod values
TokenizationnewTokenization, mintToken, whitelist, burnToken, transferFrom, transferTo, approve, dividendDistribution
STOsnewSto, newInvest, claimTokens, closeOffer

​
Read Endpoints

EndpointPurpose
GET /get-network-infoRead chain metadata and supported network configuration.
GET /get-token-infoRead token information by symbol or chain.
GET /get-tokenizer-infoRead tokenizer account information.
GET /get-stosList STOs for a token.
GET /get-sto-by-idRead one STO by ID.
GET /get-investments-by-sto-idList investments for one STO.
GET /get-investor-infoRead investor status by token and email.
GET /get-allowanceRead allowance between owner and spender.
GET /get-balance-whitelistRead investor balance and whitelist status.
GET /get-whitelist-statusCheck whether an investor wallet is whitelisted.
GET /get-sto-balanceRead STO balance and status.
GET /get-dividend-distributionRead dividend distribution information.
GET /get-transaction-statusPoll a submitted blockchain transaction.
curl --request GET \
  'https://api.sandbox.brickken.com/get-network-info?chainId=11155111' \
  --header 'x-api-key: YOUR_BRICKKEN_API_KEY'

​
Networks

Pass chainId as decimal or hex. Client tooling normalizes common values.
NetworkDecimalHex
Ethereum mainnet10x1
Base mainnet84530x2105
BNB Smart Chain560x38
Polygon mainnet1370x89
Sepolia testnet111551110xaa36a7
Polygon Amoy testnet800020x13882
Prepared transactions are on-chain actions. Verify chainId, signerAddress, token symbol or token address, and all recipient addresses before signing.