The official 2025 tokenization report is now available
Access now
September 17, 2025

Introducing Brickken API V2: Faster, Simpler, and Ready for the Future

At Brickken, we’re committed to empowering businesses and developers to seamlessly integrate tokenization into their platforms. Today, we’re thrilled to announce the rollout of Brickken API V2, a major step forward that makes integrations simpler, more consistent, and more powerful.

‍

This update streamlines the way you work with our API, prepares the ground for upcoming features, and ensures your projects can scale with ease.

Welcome to API V2 – The Next Generation

Today’s Agenda:

  • Overview of V2 improvements
  • Breaking changes you need to know
  • New powerful features
  • Step-by-step migration guide

Why migrate?

  • Simplified integration
  • New STO capabilities
  • Enhanced performance

What’s New in API V2

Feature V1 V2 Benefit
Endpoint Names /prepare-api-transactions /prepare-transactions Cleaner, shorter URLs
Transaction Flow Complex parameters Simple txId system Reduced complexity
STO Support Not available Full workflow Complete investment platform
On-Behalf Operations Not available In progress (3 endpoints) Manage user operations

1. Unified Send Transactions

We’ve simplified transaction handling with a single unified endpoint:

POST /send-transactions

‍

This works across all prepared methods: newTokenization, mintToken, whitelist, burnToken, transferFrom, transferTo, approve, dividendDistribution, and the new STO methods.

Request body (now unified):

1{
2  "signedTransactions": ["0x..."],
3  "txId": "<txId from prepare-transactions>"
4}

2. Prepare Response Now Includes txId

When you prepare transactions, you’ll now get both:

1{
2  "txId": "tx_abc123def456",
3  "transactions": [
4    {
5      "value": "0",
6      "gasLimit": "500000",
7      "maxFeePerGas": "20000000000"
8    }
9  ]
10}

Key benefits:

  • Added txId for tracking
  • Cleaner, simpler structure
  • No more BigNumber objects

3. Endpoint Naming Clean-up

We’ve simplified endpoint naming by removing the -api suffix:

  • POST /prepare-api-transactions → POST /prepare-transactions
  • POST /send-api-transaction → POST /send-transactions
  • GET /get-api-transaction-status → GET /get-transaction-status

4. Field Rename: symbol → tokenSymbol

In all prepare bodies (including newTokenization and others), please now use tokenSymbol instead of symbol.

Example:

1{ "tokenSymbol": "EXMPL" }

5. Send Transaction Simplification

V1 (Complex – Many Parameters):

1{
2	"signedTransactions": ["0x123..."],
3    "chainId": "aa36a7",  "method": "newTokenization",
4    "tokenSymbol": "ABC",
5    "tokenizerEmail": "[email protected]"
6    // ... many more parameters
7}

‍

V2 (Simple – Just 2 Parameters!):

1{ 
2  "signedTransactions": ["0x123..."],
3  "txId": "tx_abc123def456"
4}

6. New Features

🔹 Complete STO Workflow

API V2 introduces full support for Security Token Offerings (STOs).

Create STO:

1{
2  "method": "newSto",
3  "tokenSymbol": "EXMPL",
4  "price": "100",
5  "minInvestment": "10",
6  "maxInvestment": "10000",
7  "startDate": "2024-01-01T00:00:00Z",
8  "endDate": "2024-12-31T23:59:59Z",
9  "softCap": "50000",
10  "hardCap": "500000"
11}

‍

Invest in STO:

1{
2  "method": "newInvest",
3  "tokenSymbol": "EXMPL",
4  "investorEmail": "[email protected]",
5  "amount": "1000"
6}

‍

Claim Tokens:

1{  
2  "method": "claimTokens",  
3  "tokenSymbol": "EXMPL",  
4  "investorEmail": 
5  "[email protected]"
6}

🔹 On-Behalf Endpoints (In Development)

We’re introducing on-behalf operations to enable you to act directly for your users:

  • POST /create-token-on-behalf
  • POST /invest-on-behalf
  • POST /sto-claim-on-behalf

Use cases include:

  • Platform-managed investments
  • Automated token distribution
  • Simplified user experience

⚠️ These endpoints are still in development; availability and parameters may evolve.

🔹 Enhanced Data Access

New GET endpoints for better visibility:

Endpoint Purpose Example Response
/get-allowance Check token allowances { "allowance": "1000000" }
/get-balancewhitelist Balance + whitelist status { "balance": "500", "isWhitelisted": true }
/get-network-info Network info { "chainId": "0x89", "name": "Polygon" }
/get-token-info Token details { "name": "Token", "totalSupply": "1000000" }
/get-tokenizer-info Tokenizer data { "email": "...", "tokens": [...] }

Migration Steps – Your 5-Step Plan

  1. Update URLs (remove api)
// Old
const url = '<https://api.sandbox.brickken.com/prepare-api-transactions>';
// New
const url = 'https://api-sandbox.brickken.com/prepare-transactions';
  1. Rename symbol → tokenSymbol in prepare bodies

  2. Persist txId from prepare responses

  3. Use unified send body
await api.send({ signedTransactions: signed, txId });
  1. Ensure chainId values are hex with 0x prefix
    • Old: "aa36a7"
    • New: "0xaa36a7"

✅ Always test in Sandbox first: https://api-sandbox.brickken.com

Benefits Summary

  • 90% fewer parameters in send requests
  • Unified flow across all methods
  • Cleaner endpoint names (tokenSymbol, shorter URLs)
  • Full STO functionality
  • On-behalf operations for platform management
  • Rich new GET endpoints for better insights
  • Future-ready architecture

Migration Timeline

We recommend migrating within the next 1–2 weeks.

V1 will remain available during this period to support a smooth transition, after which V2 will become the standard.

Resources & Support

We’re here to help you every step of the way from Sandbox testing to production migration.
‍

Brickken API V2 is built to make tokenization integrations easier, faster, and future-ready.

‍
We can’t wait to see what you build with it.

‍

By
-