Overview
The Kuest API provides programmatic access to prediction market data, trading operations, and user management. Built on Next.js API routes, it offers a RESTful interface for interacting with markets, placing orders, and managing positions.Base URL
All API requests are made to:Available Endpoints
The API is organized into several categories:Markets & Events
GET /api/events- List prediction markets and eventsGET /api/events/[slug]/related- Get related eventsGET /api/events/[slug]/market-metadata- Get market metadataGET /api/markets/status- Check market resolution statusPOST /api/markets/status- Batch check market status
Trading & Orders
GET /api/open-orders- Get user’s open ordersGET /api/event-activity- Get trading activity for a marketGET /api/holders- Get top position holders
User Management
GET /api/users- Search for usersGET /api/notifications- Get user notificationsPUT /api/notifications/[id]- Update notification statusGET /api/affiliate-info- Get affiliate information
Market Data
GET /api/price-reference/live-series- Get live price dataGET /api/sync/volume- Sync volume dataGET /api/sync/events- Sync event data
Response Format
All API responses return JSON with a consistent structure.Success Response
Error Response
400- Bad Request (invalid parameters)401- Unauthorized (authentication required)404- Not Found500- Internal Server Error
Rate Limits
API requests are subject to the following limits:- Public endpoints: No authentication required, general rate limiting applies
- Authenticated endpoints: Require valid authentication headers
- Batch endpoints: Limited to specific batch sizes (e.g., 500 condition IDs)
Rate limits are enforced at the infrastructure level. If you need higher limits for production use, contact support.
Pagination
Many list endpoints support pagination using offset-based pagination:offset- Number of items to skip (default: 0)limit- Maximum items to return (varies by endpoint, typically 10-50)
next_cursor for pagination:
Filtering & Search
Endpoints support various query parameters for filtering:Common Parameters
| Parameter | Type | Description |
|---|---|---|
locale | string | Language code (e.g., en, es, default: en) |
offset | integer | Pagination offset (default: 0) |
limit | integer | Results per page (default varies by endpoint) |
search | string | Search query string |
status | string | Filter by status: active, resolved |
Error Codes
The API uses standard HTTP status codes:| Code | Meaning | Description |
|---|---|---|
| 200 | OK | Request succeeded |
| 400 | Bad Request | Invalid parameters or request format |
| 401 | Unauthorized | Authentication required or invalid |
| 404 | Not Found | Resource does not exist |
| 500 | Internal Server Error | Server error occurred |
Common Error Messages
Bad Request
Unauthorized
Server Error
Data Types
Micro Units
Monetary amounts and share quantities are represented in micro units (1/1,000,000):Prices
Market prices are represented as decimals between 0 and 1:0.75= 75% probability / 75¢ per share0.25= 25% probability / 25¢ per share
Timestamps
All timestamps are ISO 8601 formatted strings:Environment Variables
The API relies on several environment variables:Next Steps
Authentication
Learn how to authenticate API requests
Markets API
Start querying market data
Trading API
Place and manage orders
Integration Guide
Build trading bots and integrations