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

Supabase Integration

If preferred for internal builds, dashboards, or analytics, Liquid can provision a Supabase client to allow read-only access to certain platform data (under strict security rules).

With this option, developers can:

  • Subscribe to Postgres database changes in real time.

  • Listen to specific tables — for example:

    • Assets table: Get a real-time feed of new tokenized assets, status changes, or asset updates.

    • Marketplace trades: Monitor executed trades instantly.

This eliminates the need for constant API polling, enabling high-efficiency, real-time applications.


Supabase’s client libraries also support:

  • User Authentication: Developers can integrate Liquid’s authentication into their own apps using JWTs issued by Liquid’s auth system, Allowing users to log in via your platform while staying connected to their verified Liquid account.


This hybrid approach — API + webhooks + direct DB access — gives developers flexibility based on their needs, whether building lightweight frontends or complex institutional dashboards.

PreviousBot Triggers and WebhooksNextInteracting with Solana Programs

Last updated 14 days ago

Page cover image