Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.oneswap.cc/llms.txt

Use this file to discover all available pages before exploring further.

OneSwap shares a portion of platform swap fees with SDK developers. Once your account is enabled for fee sharing, fees accumulate automatically on every swap made through your API keys.

​
How it works

  1. A user executes a swap through your integration
  2. The platform takes its standard fee
  3. Your configured share is credited to your developer account in the database
  4. When you collect earnings, payout is sent directly to the destination party you specify in the developer portal or admin tooling

​
Developer portal

Use the wallet-authenticated developer portal to review accumulated fees, inspect recent fee events, and initiate collections. Each collection asks for a destination Canton party and transfers directly there. The public SDK does not expose developer earnings or collection APIs. Those are account-level views and stay on the wallet-authenticated OneSwap developer portal.
Collection history is strongest for CC (Amulet) payouts. Utility-token payouts such as USDCx can use a TransferOffer flow under the hood. In those cases, a completed collection record proves that OneSwap submitted the collection transfer and received a ledger update ID, but it does not independently re-read an external destination wallet balance before marking the collection complete.
Detailed collection-history records are currently available through the backend/admin collection APIs rather than a dedicated website history view. If you collect utility tokens to an external Canton party, verify:
  • the destination wallet or pending-offer state