Liquid Finance
  • Project Overview and Mission
    • Why Tokenize Assets?
    • Liquid's Vision
  • For Institutional Investors
    • Market Opportunity and Competitive Edgetor
      • Key Advantages
      • Market-Making and Liquidity
    • Compliance and Legal Framework
      • Jurisdictional Legal Wrappers
      • KYC/AML and Investor Accreditation
      • Regulatory Engagement
      • Audits and Security Compliance
      • Transparency and Reporting:
      • Commitment
    • Liquid Finance Token ($LIFI)
      • Fee Reduction
      • Staking and Yield
        • Network Security / Participation
        • Incentivizing Engagement
      • Marketplace and Liquidity Incentives
        • Boosting Listings
        • Liquidity Minting
        • Trading Fee Rewards
      • Governance
      • LiquidChain Native Token
      • Supply and Emissions
      • Value Proposition for Investors
      • Summary
  • For Developers
    • Technical Architecture Overview
      • Solana Blockchain
      • Node.js Backend
      • Supabase (PostgreSQL) Database
      • AI-Powered Bot
      • KYC/AML Integration (Civic & Sumsub)
      • Documint (Legal Document Generation)
      • Decentralized Storage (IPFS/Arweave)
    • Architecture Summary
    • Smart Contracts Documentation
    • Developer API and Integration
      • Asset Tokenization API
      • User Management and KYC API
      • Marketplace API
      • Bot Triggers and Webhooks
      • Supabase Integration
      • Interacting with Solana Programs
  • For General Users (Asset Owners & Investors)
    • Getting Started with Liquid
    • Fees, Costs and Staking Benefits for Users
    • The Liquid Vault (User Dashboard) – MVP Walkthrough
    • Staking & Rewards
  • Roadmap and Future Plans
    • Q2 2025 – Launch and MVP Expansion
    • Q3–Q4 2025 – Growth and Feature Development
    • 2026 – LiquidChain and Decentralization
    • Late 2026 and Beyond – Scaling to New Horizons
    • Summary of Roadmap Highlights
  • SOCIALS
    • Social Links
Powered by GitBook
On this page
  1. For Developers
  2. Developer API and Integration

Asset Tokenization API

Liquid's APIs allow developers to create and manage tokenized assets via simple HTTP endpoints. Example endpoints include:


  • POST /api/assets/tokenize Submit a new asset for tokenization. The payload includes:

    • Owner information

    • Asset details (type, value, jurisdiction, etc.)

    • Token parameters (name, total supply, symbol, etc.)

    Upon submission, the Liquid backend will:

    • Initiate KYC verification (if not already completed for that user)

    • Begin legal document generation

    • Start asset onboarding processes.

    The API responds with a tracking ID for the tokenization workflow.


  • GET /api/assets/{id} Retrieve the status and details of a tokenization request or minted asset. This can show:

    • Steps completed (e.g., KYC, Legal Setup, Minting Status)

    • Final minted token's address once deployment is complete.

    • Links to metadata or legal documentation if available.


  • POST /api/assets/{id}/distribute (Planned) Distribute minted tokens to a list of wallet addresses. For example, if an asset owner wants to send shares to investors.

    The payload would include:

    • A list of Solana wallet addresses.

    • Corresponding amounts of tokens for each address.

    The backend would:

    • Create the necessary token transfer transactions.

    • Verify KYC compliance for each recipient before transferring tokens.


These APIs are designed to make integrating Liquid into external apps or scaling tokenization workflows easy and programmatic — whether you're a fintech company, a real estate platform, or an institutional partner.

PreviousDeveloper API and IntegrationNextUser Management and KYC API

Last updated 14 days ago

Page cover image