Submit Signed Transactions

curl --request POST \
  --url https://api.sandbox.brickken.com/send-transactions \
  --header 'Content-Type: application/json' \
  --header 'x-api-key: <api-key>' \
  --data '{
  "signedTransactions": [
    "<string>"
  ],
  "rpcUrl": "{URL_TO_RPC} but can be omitted",
  "chainId": "aa36a7",
  "method": "newTokenization"
}'

{
  "txResponses": [
    {
      "hash": "<string>",
      "from": "<string>",
      "to": "<string>",
      "data": "<string>",
      "type": "<string>",
      "statusTx": "<string>"
    }
  ]
}

Transaction Endpoints

Send Transactions

Description: This endpoint sends signed transactions to the blockchain.

Headers:

x-api-key: YOUR_API_KEY
Content-Type: application/json

Common Request Body Parameters:

signedTransactions (array): Array of signed Ethereum transactions (as hex strings).
rpcUrl (string, optional): RPC URL of the blockchain network. If not provided, a default is used.
chainId (string): Blockchain network Chain ID in hex format (e.g., “aa36a7”).
method (string): Operation to be performed. Possible values: newTokenization, mintToken, whitelist, burnToken, transferFrom, transferTo, approve, dividendDistribution, newSto.

Method: newTokenization Sends a transaction to create a new token and start the tokenization process.

Additional Request Body Parameters:

tokenName (string)
tokenSymbol (string)
tokenizerCompanyName (string)
tokenizerName (string)
tokenizerMiddleName (string, optional)
tokenizerSurname (string)
tokenizerSecondSurname (string, optional)
tokenizerEmail (string)
tokenizerAddress (string)
supplyCap (string)
initialShareholders (array, optional): Each object includes:
- walletAddress (string)
- amount (string)
- email (string)

Method: mintToken Sends transactions to mint tokens to users.

Additional Request Body Parameters:

investorAddress (string)
investorEmail (string)
tokenSymbol (string)
needInvestorCreation (boolean)
newInvestor (object, optional): If creation is needed:
- type (string, optional): “INVESTOR_PERSON” or “INVESTOR_BUSINESS”
- name (string)
- middleName (string, optional)
- surname (string)
- secondSurname (string, optional)

Method: whitelist Whitelists a user for a token.

Additional Request Body Parameters:

tokenSymbol (string)
investorAddress (string)
investorEmail (string)
needInvestorCreation (boolean)
newInvestor (object, optional): Same structure as above

Method: burnToken Burns tokens from a user’s balance.

Additional Request Body Parameters:

tokenSymbol (string)
investorEmail (string)

Method: transferFrom Transfers tokens from one wallet to another using allowance.

Additional Request Body Parameters:

tokenSymbol (string)
from (string): Address from which tokens are transferred
to (string): Destination address
amount (string)

Method: transferTo Transfers tokens from the signer to a recipient.

Additional Request Body Parameters:

tokenSymbol (string)
to (string)
amount (string)

Method: approve Approves a spender to use tokens.

Additional Request Body Parameters:

tokenSymbol (string)
spenderAddress (string)
amount (string)
tokenizerAddress (string, optional): Required if tokenSymbol is BKN, USDT, or USDC

Method: dividendDistribution Distributes payment tokens to token holders.

Additional Request Body Parameters:

tokenSymbol (string)
amount (string)

Method: newSto Creates a new STO (Security Token Offering).

Additional Request Body Parameters:

tokenAmount (string)
tokenizerEmail (string)
offeringName (string)
startDate (string)
endDate (string)
acceptedCoin (string)
minRaiseUSD (string)
maxRaiseUSD (string)
minInvestment (string)
maxInvestment (string)
signerAddress (string)

POST

/

send-transactions

Submit Signed Transactions

curl --request POST \
  --url https://api.sandbox.brickken.com/send-transactions \
  --header 'Content-Type: application/json' \
  --header 'x-api-key: <api-key>' \
  --data '{
  "signedTransactions": [
    "<string>"
  ],
  "rpcUrl": "{URL_TO_RPC} but can be omitted",
  "chainId": "aa36a7",
  "method": "newTokenization"
}'

{
  "txResponses": [
    {
      "hash": "<string>",
      "from": "<string>",
      "to": "<string>",
      "data": "<string>",
      "type": "<string>",
      "statusTx": "<string>"
    }
  ]
}

Submits signed transactions to the blockchain. This endpoint works uniformly for all transaction types prepared using the /prepare-transactions endpoint.

Parameters

Parameter	Type	Required	Description
`signedTransactions`	string[]	Yes	Array of signed transaction hex strings
`txId`	string	Yes	Transaction ID from prepare-transactions response

Request Body

{
  "signedTransactions": [
    "0x02f8b1018203e8843b9aca00850ba43b740082520894742d35cc6634c0532925a3b8d4c9db96c4b4d8b80b844a9059cbb000000000000000000000000456789abcdef..."
  ],
  "txId": "tx_abc123def456"
}

Response

Success Response

{
  "txHash": "0x1234567890abcdef...",
  "status": "pending"
}

Error Response

{
  "error": {
    "code": "INVALID_SIGNATURE",
    "message": "Transaction signature is invalid",
    "details": {
      "transactionIndex": 0,
      "expectedSigner": "0x742d35Cc6634C0532925a3b8D4C9db96c4b4d8b",
      "actualSigner": "0x..."
    }
  }
}

Workflow

Prepare Transactions: First, call /prepare-transactions with your desired method and parameters
Sign Transactions: Sign each transaction in the returned transactions array using your preferred wallet or signing method
Send Transactions: Submit the signed transactions along with the txId to this endpoint

Supported Transaction Types

This endpoint accepts signed transactions for all methods supported by /prepare-transactions:

newTokenization - Create new tokenized assets
newSto - Create Security Token Offerings
newInvest - Make investments in STOs
claimTokens - Claim tokens from completed STOs
closeOffer - Close active STOs
mintToken - Mint additional tokens
whitelist - Manage address whitelist status
approve - Approve token spending
burnToken - Burn tokens
transferFrom - Transfer tokens (with approval)
transferTo - Transfer tokens from signer
dividendDistribution - Distribute dividends

Transaction Status

After submitting transactions, you can check their status using the /get-transaction-status endpoint with the returned transaction hash.

Security Notes

Always verify transaction details before signing
Ensure the txId matches the one received from /prepare-transactions
Use secure signing methods for production environments
Never share private keys or expose them in client-side code

Authorizations

x-api-key

string

header

required

Body

application/json

signedTransactions

string[]

Array of signed Ethereum transactions (as hex strings).

rpcUrl

string

The RPC URL to use for sending transactions. Defaults to network-based configuration if not provided.

Example:

"{URL_TO_RPC} but can be omitted"

chainId

string

Chain ID representing the blockchain network where transactions are to be executed.

Example:

"aa36a7"

method

string

Transaction type. Must be one of newTokenization, mintToken, whitelist, burnToken, transferFrom, transferTo, approve, dividendDistribution.

Example:

"newTokenization"

Response

200 - application/json

Successful response

txResponses

object[]

Show child attributes

Prepare Transactions Create Token on Behalf