Getting Started
1
Explore the API
No authentication required for public market data. Start experimenting:
GET /markets- See available marketsGET /markets/{id}- Get detailed market infoGET /markets/{id}/orderbook- View current liquidity- Test WebSocket connections for real-time feeds
2
Build Locally
While the platform is in development:
- Mock market data for testing
- Design your integration architecture
- Plan data flows and error handling
- Prepare for API launch
3
Go Live
When the production API launches:
- Connect to live endpoints
- Monitor rate limits in response headers
- Implement proper error handling
- Deploy your integration
Best Practices
Caching Cache data that doesn’t change frequently:- Market metadata (question, expiry, category)
- Historical trade data
- Current prices - every 5–10 seconds
- Order book depth - real-time via WebSocket
- Volume statistics - every minute
- Implement automatic reconnection
- Use exponential backoff (1s, 2s, 4s, 8s…)
- Resubscribe to channels after reconnection
- Consider max retry attempts before alerting
Error Handling
Smart retry logic:- 5xx errors - Retry with backoff (server issue, likely temporary)
- 4xx errors - Don’t retry (client error, fix your request)
- 429 (Rate Limit) - Respect
Retry-Afterheader, then retry - Network errors - Retry with backoff
Rate Limit Management
Stay under limits:- Track requests per minute locally
- Check
X-RateLimit-Remainingheader - Back off before hitting the limit
- Use WebSocket for real-time data instead of polling