Tips

Are trading bots allowed on Kalshi and Polymarket?

Yes. Kalshi and Polymarket both publish official APIs for placing orders from a program. What they limit is who may trade, how fast, and from where. Each rule, from the venues' own documents, as of 16 November 2026.

Published
Author
Ben
Filed under
Tips

Yes. Kalshi and Polymarket both publish official APIs for placing orders from a program, along with their own software libraries for it. A bot is a supported way to trade on both. What each venue limits is who may trade, how fast, and from where.

Every rule below comes from the venue’s own documents, and we read them on 16 November 2026. Both venues change their APIs often, so check the linked page before you build on any of it.

Kalshi

Kalshi’s API documentation covers market data and trade execution for its event contracts over REST, WebSocket and FIX. Kalshi publishes SDKs for Python and TypeScript. The packages are kalshi_python_sync, kalshi_python_async and kalshi-typescript, and the old kalshi-python package is deprecated. Using the API means accepting Kalshi’s Developer Agreement, so read it before you build.

How fast. Every authenticated request costs tokens, and your tier sets how fast the budget refills. Most requests cost 10 tokens. A 429 response means the limit was hit, and Kalshi’s advice is to back off exponentially. The tiers, from its rate limits page:

Tier Read, tokens a second Write, tokens a second
Basic 200 100
Advanced 300 300
Expert 600 600
Premier 1,200 1,200
Paragon 2,400 2,400
Prime 4,800 4,800
Prestige 12,000 9,600

A safety net from the venue. Kalshi’s order groups cancel orders automatically when a contracts limit is reached within a rolling 15 seconds. A bot should still carry its own limits. An order group is a second line behind them.

Market makers. Kalshi has designated market makers who agree to quote both sides. Its market maker program page sets quoting and volume requirements. Firms that meet them “may receive reduced fees and certain adjusted position limits”.

Polymarket

Polymarket publishes official SDKs: @polymarket/client for TypeScript and polymarket-client for Python. Its changelog says the older Python CLOB client is deprecated.

Who may trade. The international platform’s terms bar trading by people who live or are located in the United States, and in other places. Its developer docs list the US as close-only. In their words, users “can close existing positions but cannot open new ones, on both the frontend and the API”. The docs also publish a geoblock check. “Orders submitted from blocked regions will be rejected”, so a bot should call it before it trades.

Polymarket US is a separate venue. It is a designated contract market under CFTC oversight, with its own API. A bot built for one does not trade on the other.

What changed in 2026. The order book moved to CLOB V2 on 28 April 2026, with no compatibility for V1. Trades now settle in pUSD, a USDC-backed token on Polygon, which replaced USDC.e (changelog). The next change starts on 23 November 2026. New markets begin trading on Protocol V2 in phases, with new order signing (migration guide). A bot written for V1 won’t work as it is. Nor will one written for the old collateral.

Co-location. The geoblock page also sets a rule for faster access. Co-location “is available to market makers and individual traders operating on their own account”. It is not available to “third-party applications executing trades on behalf of end users”.

What that means for a bot

The venues allow bots. So the questions before you build one are practical:

  1. Are you allowed to trade there at all? Check the venue’s eligibility rules for your country before any code. On Polymarket, call the geoblock check from the server the bot runs on.
  2. Is it your own account? A bot that trades your account by your rules is the case both venues document. A service that trades for other people raises other questions, about the venue’s terms and about the law where you are.
  3. Does it respect the limits? Budget requests against the rate limits, and back off on a 429. A bot that gets throttled can’t cancel when it needs to.
  4. Is it current? Keep a link to the venue’s page next to every piece of code that depends on it. On Polymarket, check the order signing against the Protocol V2 guide.

Being allowed to run a bot is a different question from whether the bot makes money. A backtest can look good for reasons that have nothing to do with the market. We wrote up how to tell if a backtest is overfit.

We build prediction market bots to a client’s own strategy, for the venue their account is on. The details are on our prediction market bots page.

Start a conversation

Have a strategy you want to automate?

Book a strategy call