Overview
REST API endpoints for the Vezta trading platform
The Vezta API is a RESTful API built with NestJS and Fastify. All endpoints are prefixed with /api/v1/.
Base URL
- Production:
https://backend.vezta.io - Local Development:
http://localhost:3001
Authentication
Most endpoints require a JWT access token in the Authorization header:
Authorization: Bearer <access_token>Public endpoints (marked with @Public()) do not require authentication. See the Authentication section for the full wallet-based auth flow.
Response Format
All successful responses return JSON. All error responses follow a standardized format:
{
"statusCode": 400,
"code": "VALIDATION_ERROR",
"message": "Description of what went wrong"
}See Error Codes for the full list.
API Sections
Getting Started
- Overview - This page: base URL, auth header, response format
- Authentication - Wallet-based auth, Google OAuth, JWT lifecycle
- Error Codes - Machine-readable error codes and handling patterns
Users & Onboarding
- User - Profile, email verification, preferences, API keys, connected wallets
- KYC - Identity verification with document upload and selfie verification
- Waitlist - Signup, status tracking, referral stats
- Push Notifications - Device token registration for push notifications
Market Data
- Markets - Browse, search, filter, charts, order books, comments, activity
- Events - Event groups and categories with multi-market data
- Matches - Sports fixtures, live scores, standings, win probability
- Calendar - Calendar events with associated prediction markets
- Feed - Aggregated news and market-related content
- Search - Unified search across markets, events, and traders
- Analytics - Protocol overview and per-protocol breakdown
- App Version - Application version check by platform
Trading
- Orders - Order placement, management, cancel, TP/SL
- DFlow - On-chain order flow with DFlow integration
- Merge & Split - Polymarket conditional token merge and split operations
Automated Strategies
- Sniper - Auto-executing orders on new market listings
- Counter Trade - Automated opposite-side trading rules
- Combos - Multi-leg combo / RFQ (parlay-style) orders
- Arbitrage - Cross-venue arbitrage opportunity scanning
- Arbitrage Match - Cross-platform arbitrage groups (Polymarket ↔ Kalshi)
Portfolio & Wallets
- Portfolio - Positions, orders, watchlist, PnL, chart data
- Account - Deposits, withdrawals, transactions, fiat on-ramp
- Wallet - Sub-wallet creation, funding, withdrawals, token approvals
Social & Copy Trading
- Leaderboard - Global rankings, biggest wins, trader profiles
- Tracker - Follow wallets, monitor positions and trades in real time
- Wallet Lists - Custom address lists, previews, aggregated trades
- Copy Trade - Subscribe, manage, view performance history
- Activity - User activity feed
Signals & AI
- Monitor - AI-powered market signals, system health
- AI Predictions - Model-generated predictions with accuracy stats
- Insider Signals - Insider trading signal feed and feedback
- Agent Chat - Conversational AI assistant with streaming responses
- Research - Web-research reports on markets and events
- Alerts - Market price alert management
Sharing & Rewards
- Share Card - PnL cards, market cards, background management
- Share Card (Public) - Published card retrieval
- Rewards - Points, missions, challenges, referral tree
- Notifications - In-app notification management
Admin & System
- Admin - Dashboard, user/access key management, analytics, revenue
- Health - Service health check and runtime diagnostics
- Telegram - Bot webhook receiver and account linking
- Help - FAQ and help content
OpenAPI Spec
The full OpenAPI 3.0 specification is available at /docs-json on the running backend server and is used to auto-generate TypeScript clients.