May 8, 2025

Brickken API v1.0.1 – Major Update Breakdown

At Brickken, we’re committed to helping companies tokenize real-world assets (RWAs) through a seamless, developer-friendly infrastructure. With the release of API version 1.0.1, we’re introducing new capabilities that allow you to better manage tokenization lifecycles — including STO creation, investor onboarding, and document handling — while tightening consistency and clarity throughout the entire API.

‍

Let’s dive into what’s new, what’s improved, and how these changes can supercharge your tokenization experience.

‍

🚀 New Endpoints

‍

✅ PATCH /patch-api-token-docs

This endpoint provides a much-needed solution for token administrators to update key token-related documents programmatically. It's perfect for projects looking to upload or update:

  • Token logotype: JPEG or PNG file uploaded to S3.
  • Subscription agreement: Legal PDF uploaded to IPFS.
  • Legal documentation: Supplementary PDF materials (terms, disclaimers, etc.), also uploaded to IPFS.

‍

By handling both branding and compliance materials, this endpoint closes the loop on post-tokenization documentation needs.

🔐 Requires a valid x-api-key.

📝 Form type: multipart/form-data.

‍

📊 GET /get-api-stos

Retrieve all Security Token Offerings (STOs) associated with a given token via its tokenSymbol. This endpoint enables STO dashboards, investment analytics, and portfolio summaries.

Returns:

  • Token caps
  • Investment limits
  • STO status (UPCOMING, ACTIVE, COMPLETED)
  • Accepted payment currency (e.g., USDC)
  • Start and end dates

Ideal for real-time project tracking or investor relations panels.

‍

🔍 GET /get-api-sto-by-id/{id}

Need details about a specific offering? This endpoint allows you to query any STO by UUID, returning comprehensive information, including:

  • Offering name
  • Token price
  • Hard/soft cap
  • Per-investor min/max limits
  • Dates and payment methods

Perfect for onboarding flows, compliance checks, or progress reports.

‍

🔄 Enhancements to Existing Endpoints

‍

🔧 POST /prepare-api-transactions

This endpoint generates unsigned transactions for tokenization-related actions. In v1.0.1, we’ve expanded its capabilities with:

‍

🆕 New Supported Method: newSto

A major feature addition, this method allows developers to prepare transactions for launching Security Token Offerings directly from the backend.

‍

Parameters now accepted for newSto:

  • tokenizerEmail: Who created the token
  • tokenAmount: How many tokens are offered
  • offeringName: Internal or investor-facing name
  • startDate / endDate: Time-bounded investment window
  • acceptedCoin: Currency accepted for investment (USDT, USDC, etc.)
  • minRaiseUSD / maxRaiseUSD: Soft cap and hard cap
  • minInvestment / maxInvestment: Per-investor limits
  • signerAddress: Token owner's wallet

These fields allow for a fully customizable, chain-agnostic STO to be constructed off-chain and signed securely before submission.

‍

📤 POST /send-api-transactions

This endpoint is used to send signed transactions to the blockchain and Brickken backend. In v1.0.1, we've made it smarter and more robust:

  • ✅ Full support for newSto method
  • ✅ Enhanced validation when working with tokens like BKN, USDT, USDC — now requiring a valid tokenizerAddress for approvals
  • ✅ Order-sensitive submission for compound flows (e.g., whitelist before mint)

💡 Tip: If you're sending a batch like [whitelistUser1, mintUser1], [whitelistUser2, mintUser2]... make sure your transaction array is ordered accordingly.

‍

🧼 Other Improvements & Refinements

We’ve also gone under the hood to make the API easier to use:

✍️ Documentation & Clarity

  • Introduced collapsible method-specific sections in the Swagger UI
  • Expanded all method documentation to clarify intent, context, and preconditions
  • Improved examples across request bodies and responses

🔐 Security & Consistency

  • Standardized schema structures across all request bodies
  • Added missing validation and stricter checks in approval workflows

🧪 Better Developer Experience

  • All example values now match realistic usage scenarios
  • More precise descriptions for edge cases and optional fields

‍

🔗 Where to Access

Brickken API is available in two environments:

‍

📨 Final Notes

This release is a stepping stone toward even more advanced features around token lifecycle automation, investor flows, and compliant STO issuance. We’re incredibly thankful to the developer community for the feedback that led to this release — and we’re already working on what comes next.
‍

Have questions or need help integrating the new features?

📩 Reach out to us at [email protected]
‍

Stay tokenized, The Brickken Tech Team

‍

The official 2025 tokenization report is now available
Access now