Skip to main content
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": "0x02f8b1018203e8843b9aca00850ba43b740082520894742d35cc6634c0532925a3b8d4c9db96c4b4d8b80b844a9059cbb000000000000000000000000456789abcdef...",
  "txId": "0x11769b5c2028a8ed0a3bdc7599e244aee68e2cae80261d8954e44c3b5cb621a4"
}
'
{
  "txHash": "0x1234567890abcdef...",
  "status": "pending"
}
Submits signed transactions to the blockchain. This endpoint works uniformly for all transaction types prepared using the /prepare-transactions endpoint. For x402-eligible agentic methods, this endpoint can be authenticated with either x-api-key or x402 payment. To use x402, omit x-api-key, read the PAYMENT-REQUIRED header from the 402 response, then retry with X-Payment.

​
Parameters

ParameterTypeRequiredDescription
signedTransactionsstring | string[]YesSigned transaction hex string(s) starting with 0x. Can be a single string (legacy) or an array of strings
txIdstring | string[]YesTransaction ID(s) from prepare-transactions response. Must match the format of signedTransactions (both strings or both arrays)
[!IMPORTANT] signedTransactions must be a hex string (starting with 0x), not an object or array of objects. Both txId and signedTransactions must use the same format (both strings or both arrays).

​
Request Body

​
Legacy Format (Single Transaction)

{
  "signedTransactions": "0x02f8b1018203e8843b9aca00850ba43b740082520894742d35cc6634c0532925a3b8d4c9db96c4b4d8b80b844a9059cbb000000000000000000000000456789abcdef...",
  "txId": "0x11769b5c2028a8ed0a3bdc7599e244aee68e2cae80261d8954e44c3b5cb621a4"
}

​
Array Format (Multiple Transactions)

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

​
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

  1. Prepare Transactions: First, call /prepare-transactions with your desired method and parameters
  2. Sign Transactions: Sign each transaction in the returned transactions array using your preferred wallet or signing method
  3. 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 (hash) or the original transaction ID (txId) from /prepare-transactions. For x402 sends, the batch must contain only x402-eligible agentic prepared transactions and all transactions must be on the same chain.

​
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

Both txId and signedTransactions must use the same format (both strings or both arrays). signedTransactions must be hex strings starting with 0x, not objects.

​
signedTransactions
required

Signed transaction hex string(s) starting with 0x. Can be a single string (legacy) or an array of strings. Must NOT be an object or array of objects.

Example:

"0x02f8b1018203e8843b9aca00850ba43b740082520894742d35cc6634c0532925a3b8d4c9db96c4b4d8b80b844a9059cbb000000000000000000000000456789abcdef..."

​
txId
required

Transaction ID(s) from prepare-transactions response. Must match the format of signedTransactions (both strings or both arrays).

Example:

"0x11769b5c2028a8ed0a3bdc7599e244aee68e2cae80261d8954e44c3b5cb621a4"

Response

Successful response

​
txHash
string

Transaction hash of the submitted transaction

Example:

"0x1234567890abcdef..."

​
status
string

Transaction status

Example:

"pending"