Polymarket API Documentation

Introduction

Polymarket is a decentralized prediction market platform built on Ethereum (and Polygon) that allows users to bet on the outcome of real-world events using cryptocurrency. The platform leverages the Conditional Token Framework (CTF) and integrates with UMA's Optimistic Oracle to create a trustless, transparent prediction market ecosystem for DeFi betting, event forecasting, and decentralized finance applications.

How Polymarket Works

1. Market Creation: Questions about real-world events are created with multiple possible outcomes for crypto prediction markets
2. Position Trading: Users can buy and sell positions (represented as ERC-1155 tokens) based on their predictions
3. Collateral: Positions are backed by collateral tokens (typically USDC stablecoin)
4. Oracle Resolution: UMA's Optimistic Oracle system determines the outcome of prediction events
5. Payouts: Users who predicted correctly receive payouts proportional to their stakes and market liquidity

The platform uses three main smart contracts deployed on Polygon network to handle different aspects of the decentralized prediction market ecosystem:

Contract Addresses

Contract	Address	Purpose
Main Polymarket Contract	0x4d97dcd97ec945f40cf65f87097ace5ea0476045	Core prediction market logic, condition management, position splits/merges
UMA Adapter	0x65070BE91477460D8A7AeEb94ef92fe056C2f2A7	Oracle integration for question resolution and initialization
CTF Exchange	0xC5d563A36AE78145C45a50134d48A1215220f80a	Trading infrastructure for position tokens

---

Main Polymarket Contract APIs

The main contract handles core prediction market functionality including condition management, position operations, and oracle event resolution. These GraphQL APIs provide real-time blockchain data for smart contract events, trading activities, and market analytics.

1. All Available Events

Endpoint: PolyMarket - All Available Events

Get all events emitted by the main Polymarket contract to track all platform activities.

{
  EVM(network: matic) {
    Events(
      where: {LogHeader: {Address: {is: "0x4d97dcd97ec945f40cf65f87097ace5ea0476045"}}}
    ) {
      count
      Log {
        Signature {
          Name
        }
      }
    }
  }
}

Use Case: Monitor all platform activities, track user interactions, and analyze market dynamics.

Key Events Tracked:

• ConditionPreparation: When new prediction conditions are created
• ConditionResolution: When oracles resolve prediction outcomes
• PositionSplit: When users split positions into outcome-specific tokens
• PositionsMerge: When users merge outcome tokens back to collateral
• PayoutRedemption: When users claim winnings after resolution

2. Newly Created Questions/Market ID

Endpoint: PolyMarket Newly Created Questions / Market ID

Track new prediction markets as they are created on the platform.

{
  EVM(dataset: realtime, network: matic) {
    Events(
      orderBy: {descending: Block_Time}
      where: {
        Log:{
          Signature:{
            Name:{
              in:["ConditionPreparation","QuestionPrepared"]
            }
          }
        }
        LogHeader: {Address: {is: "0x4d97dcd97ec945f40cf65f87097ace5ea0476045"}}}
      limit: {count: 20}
    ) {
      Block {
        Time
        Number
        Hash
      }
      Receipt {
        ContractAddress
      }
      Topics {
        Hash
      }
      TransactionStatus {
        Success
      }
      LogHeader {
        Address
        Index
        Data
      }
      
      Transaction {
        Hash
        From
        To
      }
      Log {
        
        EnterIndex
        ExitIndex
        Index
        LogAfterCallIndex
        Pc
        SmartContract
        Signature {
          Name
          Signature
        }
      }
      Arguments {
        Name
        Value {
          ... on EVM_ABI_Integer_Value_Arg {
            integer
          }
          ... on EVM_ABI_Address_Value_Arg {
            address
          }
          ... on EVM_ABI_String_Value_Arg {
            string
          }
          ... on EVM_ABI_BigInt_Value_Arg {
            bigInteger
          }
          ... on EVM_ABI_Bytes_Value_Arg {
            hex
          }
          ... on EVM_ABI_Boolean_Value_Arg {
            bool
          }
        }
      }
    }
  }
}

Use Case:

• Monitor new market opportunities
• Build market discovery features
• Track platform growth and activity

Data Includes:

• Question text and parameters
• Market IDs for cross-referencing
• Creation timestamps
• Oracle assignments

3. Latest Resolved Questions

Endpoint: PolyMarket Latest Resolved Questions

Monitor recently resolved prediction markets and their outcomes.

{
  EVM(dataset: realtime, network: matic) {
    Events(
      orderBy: {descending: Block_Time}
      where: {
        Log:{
          Signature:{
            Name:{
              in:["ConditionResolution"]
            }
          }
        }
        LogHeader: {Address: {is: "0x4d97dcd97ec945f40cf65f87097ace5ea0476045"}}}
      limit: {count: 20}
    ) {
      Block {
        Time
        Number
        Hash
      }
      Receipt {
        ContractAddress
      }
      Topics {
        Hash
      }
      TransactionStatus {
        Success
      }
      LogHeader {
        Address
        Index
        Data
      }
      
      Transaction {
        Hash
        From
        To
      }
      Log {
        
        EnterIndex
        ExitIndex
        Index
        LogAfterCallIndex
        Pc
        SmartContract
        Signature {
          Name
          Signature
        }
      }
      Arguments {
        Name
        Value {
          ... on EVM_ABI_Integer_Value_Arg {
            integer
          }
          ... on EVM_ABI_Address_Value_Arg {
            address
          }
          ... on EVM_ABI_String_Value_Arg {
            string
          }
          ... on EVM_ABI_BigInt_Value_Arg {
            bigInteger
          }
          ... on EVM_ABI_Bytes_Value_Arg {
            hex
          }
          ... on EVM_ABI_Boolean_Value_Arg {
            bool
          }
        }
      }
    }
  }
}

Use Case:

• Track market resolution patterns
• Analyze oracle accuracy
• Calculate historical performance metrics
• Trigger payout processes

Resolution Data:

• Final outcomes and payout numerators
• Resolution timestamps
• Oracle addresses
• Market performance metrics

4. Latest Position Splits

Endpoint: Latest position Split

Track when users split their collateral into outcome-specific position tokens.

{
  EVM(dataset: realtime, network: matic) {
    Events(
      orderBy: {descending: Block_Time}
      where: {
        Log:{
          Signature:{
            Name:{
              in:["PositionSplit"]
            }
          }
        }
        LogHeader: {Address: {is: "0x4d97dcd97ec945f40cf65f87097ace5ea0476045"}}}
      limit: {count: 20}
    ) {
      Block {
        Time
        Number
        Hash
      }
      Receipt {
        ContractAddress
      }
      Topics {
        Hash
      }
      TransactionStatus {
        Success
      }
      LogHeader {
        Address
        Index
        Data
      }
      
      Transaction {
        Hash
        From
        To
      }
      Log {
        
        EnterIndex
        ExitIndex
        Index
        LogAfterCallIndex
        Pc
        SmartContract
        Signature {
          Name
          Signature
        }
      }
      Arguments {
        Name
        Value {
          ... on EVM_ABI_Integer_Value_Arg {
            integer
          }
          ... on EVM_ABI_Address_Value_Arg {
            address
          }
          ... on EVM_ABI_String_Value_Arg {
            string
          }
          ... on EVM_ABI_BigInt_Value_Arg {
            bigInteger
          }
          ... on EVM_ABI_Bytes_Value_Arg {
            hex
          }
          ... on EVM_ABI_Boolean_Value_Arg {
            bool
          }
        }
      }
    }
  }
}

Use Case:

• Monitor trading activity and market participation
• Analyze user betting patterns
• Track liquidity flows

Split Event Details:

• User addresses (stakeholders)
• Collateral tokens and amounts
• Partition arrays showing outcome distribution
• Parent collection IDs

5. Condition Resolution Events

Endpoint: PolyMarket - Condition Resolution Event

Specifically track condition resolution events when oracles determine outcomes.

{
  EVM(dataset: realtime, network: matic) {
    Events(
      orderBy: {descending: Block_Time}
      where: {
        Log:{
          Signature:{
            Name:{
              in:["ConditionResolution"]
            }
          }
        }
        LogHeader: {Address: {is: "0x4d97dcd97ec945f40cf65f87097ace5ea0476045"}}}
      limit: {count: 20}
    ) {
      Block {
        Time
        Number
        Hash
      }
      Receipt {
        ContractAddress
      }
      Topics {
        Hash
      }
      TransactionStatus {
        Success
      }
      LogHeader {
        Address
        Index
        Data
      }
      
      Transaction {
        Hash
        From
        To
      }
      Log {
        
        EnterIndex
        ExitIndex
        Index
        LogAfterCallIndex
        Pc
        SmartContract
        Signature {
          Name
          Signature
        }
      }
      Arguments {
        Name
        Value {
          ... on EVM_ABI_Integer_Value_Arg {
            integer
          }
          ... on EVM_ABI_Address_Value_Arg {
            address
          }
          ... on EVM_ABI_String_Value_Arg {
            string
          }
          ... on EVM_ABI_BigInt_Value_Arg {
            bigInteger
          }
          ... on EVM_ABI_Bytes_Value_Arg {
            hex
          }
          ... on EVM_ABI_Boolean_Value_Arg {
            bool
          }
        }
      }
    }
  }
}

Use Case:

• Automate payout calculations
• Track oracle performance
• Monitor resolution timing

Resolution Details:

• Condition IDs and outcomes
• Payout numerator arrays
• Oracle addresses and timestamps

---

UMA Adapter APIs

The UMA Adapter contract manages the integration with UMA's Optimistic Oracle system for decentralized question resolution and dispute handling. These APIs track oracle interactions, question lifecycle events, and resolution processes for prediction market outcomes.

1. All UMA Adapter Events

Endpoint: UMACFA Adapter All events

Comprehensive tracking of all UMA Adapter contract events.

{
  EVM(network: matic) {
    Events(
      where: {LogHeader: {Address: {is: "0x65070BE91477460D8A7AeEb94ef92fe056C2f2A7"}}}
    ) {
      count
      Log {
        Signature {
          Name
        }
      }
    }
  }
}

Use Case:

• Monitor oracle integration health
• Track question lifecycle from initialization to resolution
• Debug oracle-related issues

2. Question Resolved

Endpoint: UMA Adapter Question Resolved

Track when UMA oracle resolves questions with final outcomes.

{
  EVM(dataset: realtime, network: matic) {
    Events(
      orderBy: {descending: Block_Time}
      where: {
        Log:{
          Signature:{
            Name:{
              in:["QuestionResolved"]
            }
          }
        }
        LogHeader: {Address: {is: "0x65070BE91477460D8A7AeEb94ef92fe056C2f2A7"}}}
      limit: {count: 20}
    ) {
      Block {
        Time
        Number
        Hash
      }
      Receipt {
        ContractAddress
      }
      Topics {
        Hash
      }
      TransactionStatus {
        Success
      }
      LogHeader {
        Address
        Index
        Data
      }
      
      Transaction {
        Hash
        From
        To
      }
      Log {
        
        EnterIndex
        ExitIndex
        Index
        LogAfterCallIndex
        Pc
        SmartContract
        Signature {
          Name
          Signature
        }
      }
      Arguments {
        Name
        Value {
          ... on EVM_ABI_Integer_Value_Arg {
            integer
          }
          ... on EVM_ABI_Address_Value_Arg {
            address
          }
          ... on EVM_ABI_String_Value_Arg {
            string
          }
          ... on EVM_ABI_BigInt_Value_Arg {
            bigInteger
          }
          ... on EVM_ABI_Bytes_Value_Arg {
            hex
          }
          ... on EVM_ABI_Boolean_Value_Arg {
            bool
          }
        }
      }
    }
  }
}

Use Case:

• Trigger automated payouts
• Update market status in applications
• Analyze resolution patterns and timing

Resolution Data:

• Question IDs and final answers
• Resolution timestamps
• Oracle dispute information (if any)

3. New Questions Initialized

Endpoint: PolyMarket - UMA Adapter - New Questions

Monitor when new questions are initialized in the UMA oracle system.

{
  EVM(dataset: realtime, network: matic) {
    Events(
      orderBy: {descending: Block_Time}
      where: {
        Log:{
          Signature:{
            Name:{
              in:["QuestionInitialized"]
            }
          }
        }
        LogHeader: {Address: {is: "0x65070BE91477460D8A7AeEb94ef92fe056C2f2A7"}}}
      limit: {count: 20}
    ) {
      Block {
        Time
        Number
        Hash
      }
      Receipt {
        ContractAddress
      }
      Topics {
        Hash
      }
      TransactionStatus {
        Success
      }
      LogHeader {
        Address
        Index
        Data
      }
      
      Transaction {
        Hash
        From
        To
      }
      Log {
        
        EnterIndex
        ExitIndex
        Index
        LogAfterCallIndex
        Pc
        SmartContract
        Signature {
          Name
          Signature
        }
      }
      Arguments {
        Name
        Value {
          ... on EVM_ABI_Integer_Value_Arg {
            integer
          }
          ... on EVM_ABI_Address_Value_Arg {
            address
          }
          ... on EVM_ABI_String_Value_Arg {
            string
          }
          ... on EVM_ABI_BigInt_Value_Arg {
            bigInteger
          }
          ... on EVM_ABI_Bytes_Value_Arg {
            hex
          }
          ... on EVM_ABI_Boolean_Value_Arg {
            bool
          }
        }
      }
    }
  }
}

Use Case:

• Track question creation pipeline
• Monitor oracle assignment process
• Analyze question complexity and types

Initialization Data:

• Question identifiers
• Oracle parameters
• Reward and bond amounts
• Expiry times

---

CTF Exchange APIs

The Conditional Token Framework (CTF) Exchange handles the decentralized trading infrastructure for position tokens, order matching, and liquidity provision. These APIs provide access to DEX trading data including order fills, token registrations, and market making activities for prediction market tokens.

1. Token Registered Events

Endpoint: PolyMarket CTF Exchange Contract - TokenRegistered Event

Track when new outcome tokens are registered for trading.

{
  EVM(dataset: realtime, network: matic) {
    Events(
      orderBy: {descending: Block_Time}
      where: {Log: {Signature: {Name: {in: ["TokenRegistered"]}}}, LogHeader: {Address: {is: "0xC5d563A36AE78145C45a50134d48A1215220f80a"}}}
      limit: {count: 20}
    ) {
      Block {
        Time
        Number
        Hash
      }
      Receipt {
        ContractAddress
      }
      Topics {
        Hash
      }
      TransactionStatus {
        Success
      }
      LogHeader {
        Address
        Index
        Data
      }
      Transaction {
        Hash
        From
        To
      }
      Log {
        EnterIndex
        ExitIndex
        Index
        LogAfterCallIndex
        Pc
        SmartContract
        Signature {
          Name
          Signature
        }
      }
      Arguments {
        Name
        Value {
          ... on EVM_ABI_Integer_Value_Arg {
            integer
          }
          ... on EVM_ABI_Address_Value_Arg {
            address
          }
          ... on EVM_ABI_String_Value_Arg {
            string
          }
          ... on EVM_ABI_BigInt_Value_Arg {
            bigInteger
          }
          ... on EVM_ABI_Bytes_Value_Arg {
            hex
          }
          ... on EVM_ABI_Boolean_Value_Arg {
            bool
          }
        }
      }
    }
  }
}

Use Case:

• Monitor new trading pairs
• Build token registries
• Track market expansion

Registration Data:

• Token addresses and metadata
• Market associations
• Trading parameters

2. Orders Matched Events

Endpoint: PolyMarket CTF Exchange Contract - OrdersMatched Event

Monitor successful order matching and trade executions.

{
  EVM(dataset: realtime, network: matic) {
    Events(
      orderBy: {descending: Block_Time}
      where: {Log: {Signature: {Name: {in: ["OrdersMatched"]}}}, LogHeader: {Address: {is: "0xC5d563A36AE78145C45a50134d48A1215220f80a"}}}
      limit: {count: 20}
    ) {
  
      Block {
        Time
        Number
        Hash
      }
      Receipt {
        ContractAddress
      }
      Topics {
        Hash
      }
      TransactionStatus {
        Success
      }
      LogHeader {
        Address
        Index
        Data
      }
      Transaction {
        Hash
        From
        To
      }
      Log {
        EnterIndex
        ExitIndex
        Index
        LogAfterCallIndex
        Pc
        SmartContract
        Signature {
          Name
          Signature
        }
      }
      Arguments {
        Name
        Value {
          ... on EVM_ABI_Integer_Value_Arg {
            integer
          }
          ... on EVM_ABI_Address_Value_Arg {
            address
          }
          ... on EVM_ABI_String_Value_Arg {
            string
          }
          ... on EVM_ABI_BigInt_Value_Arg {
            bigInteger
          }
          ... on EVM_ABI_Bytes_Value_Arg {
            hex
          }
          ... on EVM_ABI_Boolean_Value_Arg {
            bool
          }
        }
      }
    }
  }
}

Use Case:

• Track trading volume and activity
• Analyze price discovery
• Calculate market metrics

Match Data:

• Order details and participants
• Trade amounts and prices
• Market identifiers
• Execution timestamps

3. Order Filled Events

Endpoint: PolyMarket CTF Exchange Contract - OrderFilled Event

Track individual order fills and partial executions.

{
  EVM(dataset: realtime, network: matic) {
    Events(
      orderBy: {descending: Block_Time}
      where: {Log: {Signature: {Name: {in: ["OrderFilled"]}}}, LogHeader: {Address: {is: "0xC5d563A36AE78145C45a50134d48A1215220f80a"}}}
      limit: {count: 20}
    ) {
      Block {
        Time
        Number
        Hash
      }
      Receipt {
        ContractAddress
      }
      Topics {
        Hash
      }
      TransactionStatus {
        Success
      }
      LogHeader {
        Address
        Index
        Data
      }
      Transaction {
        Hash
        From
        To
      }
      Log {
        EnterIndex
        ExitIndex
        Index
        LogAfterCallIndex
        Pc
        SmartContract
        Signature {
          Name
          Signature
        }
      }
      Arguments {
        Name
        Value {
          ... on EVM_ABI_Integer_Value_Arg {
            integer
          }
          ... on EVM_ABI_Address_Value_Arg {
            address
          }
          ... on EVM_ABI_String_Value_Arg {
            string
          }
          ... on EVM_ABI_BigInt_Value_Arg {
            bigInteger
          }
          ... on EVM_ABI_Bytes_Value_Arg {
            hex
          }
          ... on EVM_ABI_Boolean_Value_Arg {
            bool
          }
        }
      }
    }
  }
}

Use Case:

• Detailed trade analysis
• Order book reconstruction
• User trading pattern analysis

Fill Data:

• Order IDs and fill amounts
• Price execution details
• Maker/taker information
• Fee calculations

---

Developer Integration Guide

Getting Started with Polymarket APIs

1. Choose Your Data Source: Use the appropriate smart contract address based on what blockchain data you need:

   • Market events and condition management: Main Polymarket contract
   • Oracle resolution and dispute handling: UMA Adapter contract
   • Trading activity and order matching: CTF Exchange contract

2. Set Up Bitquery Access: All prediction market APIs are accessible through Bitquery's GraphQL IDE for real-time blockchain analytics

   • Sign up for a Bitquery account
   • Use the provided query links as starting points for your DeFi applications
   • Customize GraphQL queries for your specific prediction market use case

Common Use Cases for Polymarket Data

Prediction Market Discovery Application:

• Use "Newly Created Questions" API for discovering new betting markets and investment opportunities
• Subscribe to real-time blockchain updates for market creation events
• Display market metadata, odds, and betting parameters for user engagement

DeFi Trading Analytics Dashboard:

• Combine CTF Exchange APIs for comprehensive decentralized trading data and market insights
• Track trading volume, liquidity pools, and price movements across prediction markets
• Analyze user trading patterns, bet distributions, and market maker activities

Oracle Monitoring and Risk Management System:

• Use UMA Adapter APIs to track question lifecycle and resolution accuracy
• Monitor oracle resolution times, dispute rates, and consensus mechanisms
• Alert on oracle failures, delays, or potential market manipulation for risk assessment

Additional Resources

• Polymarket Official Documentation
• UMA Oracle Documentation
• Conditional Token Framework
• Bitquery GraphQL API Documentation

Support

For technical support and questions:

• Join the Bitquery Telegram

---

This comprehensive API documentation covers Polymarket's core prediction market functionality, smart contract events, and DeFi trading data through Bitquery's blockchain APIs. For real-time cryptocurrency market data, decentralized oracle information, and the most up-to-date prediction market insights, always refer to the official Polymarket documentation and verify smart contract source code on Polygon blockchain explorers.