Skip to main content

Simpfor.fun SDK Reference

Complete TypeScript SDK for the Simpfor.fun copy trading platform. Build copy trading apps, integrate trader analytics, and manage user wallets with ease.

Quick Start

Install
Basic Usage

Authentication

Send Verification Code
Verify OTP

Social Authentication

Privy Integration
Google OAuth

Copy Trading

Core Operations

Create Copy Trade
Start/Stop Copying
List Copy Trades

Performance Tracking

Get PnL History
Get Trade Details
Get Total PnL

Trader Discovery

Top Traders

Fetch All Top Traders
Paginated Top Traders
Smart Categories

Trader Analytics

Trader Snapshot
Trader Overview
Share Information

Wallet Management

KMS Wallet Operations

Check Wallet Availability
Create KMS Key
Activate KMS Wallet
List User Wallets
Refresh Agent Wallet

Builder Fee Management

Get Builder Fee Info
Bind Builder

Cross-Chain Deposits

Bridge Operations

Get/Create Bridge Address
List Bridge Addresses
Register Bridge with Permit

User Management

Watchlist

Manage Watched Traders

Referrals

Get Referral Info
Get Referral List
Claim Commission

Coupons & Rewards

Get User Coupons
Claim Coupon

Solana Integration

Get Solana Address Status
Link Solana Address

TypeScript Types

Core Interfaces

Request Types

Error Handling

Error Structure

All API errors follow this format:

Common Error Codes

  • 400: Bad Request - Invalid parameters
  • 401: Unauthorized - Authentication required
  • 404: Not Found - Resource doesn’t exist
  • 429: Rate Limited - Too many requests
  • 500: Server Error - Internal server issue

Error Handling Pattern

Rate Limits

  • Authentication: 10 requests/minute
  • Trading Operations: 60 requests/minute
  • Analytics: 100 requests/minute
  • General Endpoints: 200 requests/minute

Configuration

Environment Setup

Best Practices

Connection Management
  • Reuse SDK instances
  • Implement proper error handling
  • Use retry logic with exponential backoff
Data Management
  • Cache trader data locally when possible
  • Use pagination for large datasets
  • Implement reasonable polling intervals
Security
  • Never expose access tokens client-side
  • Use environment variables for configuration
  • Validate inputs before API calls

Support

Documentation Community
Ready to build? Check out our Integration Examples for complete implementation guides.