Skip to main content

Event Creation Overview

This section covers how prediction market events are created, configured, and managed on the Intotes platform.

Who Can Create Events​

Event creation is restricted to users with the is_creator flag enabled on their account. There are two ways to obtain creator access:

  1. Telegram Bot -- Link your account through the Intotes Telegram bot, which can grant creator permissions.
  2. Admin Assignment -- A platform administrator can assign the creator role via the admin stats endpoints (POST /api/v1/stats/role).

Regular users cannot create events directly but can submit event suggestions through the POST /api/v1/events/suggest endpoint.

Event Structure​

Intotes uses a three-level hierarchy for prediction markets:

Event
 └── Pool (one or more)
      └── Market (one or more)

Event​

The top-level container. Represents a question or scenario users can bet on (e.g., "Champions League Final 2026" or "BTC price in 1 hour"). Events hold metadata like name, tags, images, and lifecycle status.

Pool​

A pool groups related markets under an event. Each pool defines:

  • The set of market names and their initial probabilities
  • LMSR liquidity parameter (lmsr_b_kopecks)
  • Volume boundaries (volume_min_kopecks, volume_max_kopecks)
  • Optional Polymarket token IDs for odds syncing
  • Optional asset tracking fields for crypto price events

Market​

The individual outcomes users trade on. Markets are automatically created from pool metadata -- you define market_names and market_probabilities at the pool level, and the corresponding markets are generated. Each market tracks its own order book, AMM state, and positions.

Event Lifecycle Workflow​

The typical workflow for creating and managing an event:

  1. Create -- Use the API to create an event with its pools and markets (either step-by-step or all at once via create-full).
  2. Configure Pools -- Add or adjust pools, set initial probabilities, and configure LMSR parameters.
  3. Upload Image -- Attach an event image for the feed display.
  4. Activate -- Set is_active: true to make the event visible in the public feed.
  5. Monitor -- Users trade on markets. The LMSR AMM and order book handle price discovery.
  6. Close with Outcome -- When the event resolves, close it by specifying the winning outcome index. Settlement pays winners and records PnL.

Alternatively, events can be cancelled, which refunds all positions without declaring a winner.

What's Next​