Introduction

Sendy is a mobile portfolio tracking and trading platform for Solana memecoins. In the app you link wallets and track activity; from the dashboard you can create an API key to access your own wallet data in code. Integrations should call the versioned surface at /api/v2/sdk: requests use your key, count toward account quota, and only return data for wallets you are allowed to see in Sendy.

Base URL

Production routes are served from https://api.sendy.lol/api/v2. Append paths such as /sdk/wallet/positions when building URLs. Store the secret in an environment variable (for example SENDY_API_KEY); do not ship it in public clients.

Integration surface

Use GET and POST under /sdk/… for REST. Live fills stream over Socket.IO ( see Trade stream and Token stream). Other routes under /api/v2 serve the product and are not the supported contract for API keys.

Wallet data

• Wallets — addresses you may query (associated and tracked).
• Balance history — portfolio value over a timeframe.
• Positions — current token holdings and notionals.
• Token PnL — per-position performance where data exists.
• Activity — recent on-chain activity snapshot (REST).
• Mint trades — swap history for a specific mint and wallet.
• Trade stream — all fills for a wallet; Token stream — one mint only.

Official SDKs

Thin clients wrap the same routes with typed helpers for TypeScript, Rust, and Python. Install one package per language and keep keys in environment variables rather than committing them to source control.

Next steps

• Authentication — headers, quotas, errors
• SDK installation — packages and minimal usage
• Positions — smallest first request