Skip to main content

​
Prerequisites

Before starting your integration:
  • Review Key Concepts for an overview of Sonar’s architecture
  • Read the Technical Overview to understand the end-to-end purchase flow
  • Understand Entities to learn how users, entities, and wallets relate

​
Integration Approaches

Your frontend application orchestrates the complete purchase flow: user authentication, eligibility verification, requesting purchase permits, and submitting transactions onchain. Choose an approach based on your architecture.

Frontend-only

Best for: SPAs without a backendAll authentication and API calls happen client-side using React hooks. Tokens are stored in browser storage.

Frontend with Backend

Best for: Apps that already have a backendOAuth tokens are stored server-side and all Sonar API requests are proxied through your backend.
  • More secure (tokens never exposed to browser)
  • Automatic token refresh on server
  • Example app →

​
Solana (SVM)

If your sale runs on Solana, the Sonar API calls work the same way as in the guides above. Follow either approach for OAuth and entity management, then refer to the Solana guide for the chain-specific wallet adapter and transaction construction.

Solana Integration

Wallet adapter setup, PDA derivation, and place_bid transaction construction for Solana sales.

​
Testing Your Integration

Use test sales during development to simulate various entity states, including setup progress, eligibility status, and failure scenarios. Test sales allow you to verify your integration handles edge cases without completing actual verification.