Polytoolhub logoPolytoolhubSearch tools
← Data APIs

Data API

Bitquery Polymarket API

Query and stream decoded Polymarket on-chain trades, balances, market creation and settlement through Bitquery’s blockchain data platform.

4.0/ 5Editorial rating0 user reviews
Visit official sitebitquery.io
Available on
GraphQL, WebSocket, Kafka, gRPC

Screenshots and interface

Product preview1 / 2

Polymarket GraphQL datasets and example response.

What is Bitquery Polymarket API?

Bitquery is useful when the question concerns on-chain activity: who traded, which outcome tokens a wallet holds, how volume changed or when a market resolved. Its GraphQL schema combines Polymarket-specific filters with broader Polygon data, with streaming and bulk delivery options for larger pipelines.

Who it is for

  • Developers building wallet and market analytics
  • Researchers joining Polymarket activity with Polygon transactions
  • Data teams ingesting sustained event streams

Features and coverage

Available on
GraphQL, WebSocket, Kafka, gRPC
Markets & venues
Polymarket, Polygon
  • Trade queries

    Filter decoded outcome-token trades by market, wallet or protocol.

  • Outcome prices

    Read prices associated with on-chain trades.

  • Position balances

    Use balance-update datasets to study wallet exposure.

  • Market lifecycle

    Track condition creation, resolution, payouts and redemptions.

  • Aggregated volume

    Group trade activity and rank markets.

  • Delivery options

    Use GraphQL queries and WebSocket subscriptions, with Kafka, gRPC and cloud delivery options for eligible plans.

Workflows with Bitquery Polymarket API

Build a wallet monitor

Start from a narrow trade query, filter the relevant wallet and subscribe to new matching rows. Join balance updates when the display needs current token exposure.

Research market settlement

Follow condition and payout events, join redemptions and retain transaction identifiers for inspection.

Plan a historical ingestion

Specify chain, dataset, period and delivery format before choosing archive access and compute quotas.

Pricing and total cost

Self-service API plans meter points, streaming minutes and data transfer. The current annual prices are Personal $29/month equivalent, Pro $69 and Scale $199, billed yearly. Archive history is separate.

Personal — annual billing

$29/month equivalent ($348/year)

  • 100,000 API points/month
  • Personal use; no streaming

Pro — annual billing

$69/month equivalent ($828/year)

  • 1 million API points/month
  • 100,000 stream-minutes and 5 GB
  • Commercial use

Scale — annual billing

$199/month equivalent ($2,388/year)

  • 5 million API points/month
  • 2 million stream-minutes and 50 GB
  • Commercial use

Fees and usage costs

  • Monthly billing and annual commitments differ.
  • Archive add-ons are per chain and data family; published entry prices begin at $100/month or $70/month equivalent billed yearly. Polymarket-specific history requires the relevant chain/product quote.

Trial: 7-day live-data trial, no card required. Archive history is excluded.

Getting started

Before you start: On-chain trade prices describe completed activity, not resting CLOB liquidity.

  1. Create a Bitquery account and obtain an API token.
  2. Open the IDE and select a Polymarket example.
  3. Filter a small result set before expanding the query.
  4. Choose request/response or subscription delivery.
  5. Check point, streaming and archive allowances for the intended workload.

Open documentation

Useful links

What to check

  • On-chain trade prices describe completed activity, not resting CLOB liquidity.
  • Personal-plan licensing excludes commercial use.
  • The entry plans do not include a full historical archive.
  • GraphQL, Kafka, gRPC and bulk delivery have different plan and volume requirements.

A closer look

Ratings & reviews

Write a review
Editorial rating
4.0/ 5
0 user reviews
Polytoolhub editorial

Our take on Bitquery Polymarket API

Detailed on-chain query and streaming options suit data-heavy integrations. Licensing, archive coverage and several usage units require careful plan selection; this is not a resting-book feed.

Based on documented features, setup and access terms. How we rate

User reviews 0

The main score switches to user ratings after 5 published reviews.

Be the first to share your experience

A specific example helps the next person choose the right tool.

Write a review

How was your experience with Bitquery Polymarket API?

Share what you used, what worked and what could be better. We confirm your email and review the submission before publishing.

To submit a review, email info@polytradingbot.com with the tool name, your rating and your experience. Enable JavaScript to prepare a draft here.

Related tools

Browse category
DepthFeed v3 API introduction and dataset scope.
DepthFeed
Data API4.0Editorial

Retrieve full historical order books, sports market data and aligned price bars for research, replay and liquidity analysis.

  • Data coverage Order books · Prices · Sports events
  • Access API · MCP

Historical resting book depth.

Goldsky: On-chain data platform and delivery destinations.
Goldsky
Data API4.0Editorial

Send Polymarket fills, positions and balances into your database for analytics or applications.

  • Data coverage Trades · Positions
  • Access API · CLI

Operate indexed on-chain datasets and pipelines.

Polymarket Data API: Official public analytics guide.
Polymarket Data API
Data API4.0Editorial

Build wallet dashboards and market analytics from public positions, activity, trades, holders, open interest and rankings.

  • Data coverage Positions · Account activity
  • Access API

Official wallet and public analytics.

Frequently asked questions about Bitquery Polymarket API

Can it replace an order-book feed?

Its core Polymarket datasets describe on-chain activity; use a dedicated CLOB depth feed for resting orders.

Is historical data included in the basic price?

Full archive access is sold as an add-on.

Can I track redemptions as well as trades?

Yes. Settlement and lifecycle datasets cover the relevant on-chain events.