Skip to main content
This reference is not fully comprehensive yet, but includes docs on the more nuanced parts of the API like how to interpret the fields in EntityDetails.

SonarClient functions

All functions can throw an APIError.

readEntity

Reads an entity’s details by entity ID. This function is expected to throw a APIError with status 404 if the entity is not found. Arguments Returns ReadEntityResponse

listAvailableEntities

Lists all available entities for the authenticated user. Arguments Returns ListAvailableEntitiesResponse

myProfile

Fetches the authenticated user’s profile information. Arguments None. Returns MyProfileResponse

readEntityInvestmentHistory

Fetches the authenticated user’s investment history, showing all Echo private group investments they have participated in. Arguments None. Returns EntityInvestmentHistoryResponse EntityInvestment Example

fetchLimits

Fetches the commitment limits for a wallet in a sale. Use this to display the minimum and maximum commitment amounts to users. Arguments Returns LimitsResponse

prePurchaseCheck

Should be called at the start of the purchase flow to check whether there are any preconditions to purchase. Arguments Returns PrePurchaseCheckResponse

readCommitmentData

Fetches commitment data for a sale. This is a public API endpoint that does not require authentication. Arguments Returns ReadCommitmentDataResponse For auctions, the clearing price is expressed in terms of a ClearingPriceNumerator and ClearingPriceDenominator fraction. The clearing price is in smallest units of the payment token per smallest unit of the offered token. You can divide the ClearingPriceNumerator by the ClearingPriceDenominator to get the price in decimal format, but you might lose precision. The ClearingPriceMicroUSD field is provided for convenience to avoid the need to divide the numerator and denominator. It is only set if the sale is using an auction pricing strategy and the payment token is a USD stablecoin and the offered token decimals are configured. It contains the current clearing price in micro-USD for one human-readable offered token (1 human-readable token = 10^OfferedTokenDecimals smallest units). Warning: this could lose precision, so ClearingPriceNumerator and ClearingPriceDenominator should be used as the machine-readable value.

generatePurchasePermit

For onchain sales, generatePurchasePermit should be called as part of the purchase flow to generate a purchase permit to pass to the sale contract. The permit is signed by Sonar, and the contract will need to verify the signature as well as the permit data. Arguments Returns GeneratePurchasePermitResponse

Core types

EntityDetails

MyProfileResponse

EntitySetupState

Enum with possible values: not-started
  • The entity has not started the setup process. The user should be linked to the Sonar site to continue.
  • Suggested message: “Entity not ready to invest — Please complete the entity setup process.”
in-progress
  • The entity has started the setup process, but it is not yet in review. The user should be linked to the Sonar site to continue.
  • Suggested message: “Entity not ready to invest — Please complete the entity setup process.”
ready-for-review
  • The entity has completed all current steps of the setup process and is ready to submit their data for review. The user should be linked to the Sonar site to continue.
  • Suggested message: “Entity not ready to invest — Please complete the entity setup process.”
in-review
  • The Sonar team is reviewing the entity.
  • Suggested message: “Entity not ready to invest — Please wait for the review to finish before you can make investments.”
failure
  • There is a problem with the entity setup. The user should be linked to the Sonar site so they can address the issues.
  • Suggested message: “Entity not ready to invest — Review your entity status in Sonar.”
failure-final
  • There is a problem with the entity setup, and the user is not able to address the issues.
  • Suggested message: “Entity not ready to invest — Review your entity status in Sonar.”
technical-issue
  • The setup is in a known technical issue state and we want the user to contact support if this happens.
  • Suggested message: “There’s an issue with your account — Please contact Sonar support to resolve it.”
complete
  • The entity has completed the setup process.
  • Suggested message: depends on the SaleEligibility value.

SaleEligibility

Once the entity has completed setup, you should check whether they are currently eligible for the sale. Possible values: eligible
  • The entity has completed setup and is eligible for the sale.
  • Suggested message: “Your entity is ready to participate in the sale.”
not-eligible
  • If the entity doesn’t meet sale requirements (e.g. resident of a blocked jurisdiction or accredited).
  • Suggested message: “Entity not qualified to invest.”
unknown-setup-incomplete
  • We don’t know whether the entity is eligible yet because they have not completed setup.
  • Suggested message: depends on the EntitySetupState value.

InvestingRegion

This can be useful if there are additional sale conditions that apply to US/EU entities, and you want to display this to users in the UI. Enum with possible values: unknown
  • We don’t currently know the entity’s region. This is only expected to be the case before KYC/KYB is completed.
us
  • The entity is located in the United States.
eu
  • The entity is located in the European Union.
other
  • The entity is located in another region.

PrePurchaseFailureReason

Enum with possible values: unknown
  • We don’t know why the entity is not ready to purchase. This is not expected to happen.
  • Suggested message: “An unknown error occurred — Please try again or contact support.”
wallet-risk
  • The wallet does not meet the configured risk thresholds.
  • Suggested message: “The connected wallet is not eligible for this sale. Connect a different wallet.”
max-wallets-used
  • The entity has reached the maximum number of wallets allowed for this sale.
  • Suggested message: “Maximum number of wallets reached — This entity can’t use the connected wallet. Use a previous wallet.”
requires-liveness
  • The entity requires a liveness check.
  • This is an expected case and the UI should not show an error; the UI should redirect the user to the LivenessCheckURL to complete a liveness check.
sale-not-active
  • The sale is not currently in a state where purchases are allowed.
  • Suggested message: “The sale is not currently active.”
wallet-not-linked
  • The connected wallet is not linked to the entity. This suggests there is a bug on your sale website because the entity ID should be looked up from the currently connected wallet address.
outside-time-window
  • The current time is outside the sale’s configured commitment window.
  • Suggested message: “The sale is not currently accepting commitments.”

PurchasePermitV3

The current permit version with time-gated access support.

PurchasePermitV2

Legacy permit version without time-gated access. New sales should use V3.

Commitment

Represents a single commitment made to a sale. The commitment price is only of interest for variable price sales - like auctions. It is expressed in terms of a PriceNumerator and PriceDenominator fraction. The price is in smallest units of the payment token per smallest unit of the offered token. You can divide the PriceNumerator by the PriceDenominator to get the price in decimal format, but you might lose precision. The PriceMicroUSD field is provided for convenience to avoid the need to divide the numerator and denominator. It is only set if the payment token is a USD stablecoin and the offered token decimals are configured. It contains the current commitment price in micro-USD for one human-readable offered token (1 human-readable token = 10^OfferedTokenDecimals smallest units). Warning: this could lose precision, so PriceNumerator and PriceDenominator should be used as the machine-readable value.

WalletTokenAmount

Represents an amount committed from a specific wallet using a specific token.

APIError

Thrown if the Sonar API responds with a non-2xx status code or the response body fails to parse. Expected cases will be mentioned in the relevant function docs. Suggested message for unexpected errors: “Failed to load your data — Please try again or contact Sonar support.”