Update Polymarket documentation - April 9, 2026
Changes: - Changelog: Added Apr 9, 2026 entry - GET /markets: closed defaults to false - list-markets.md: Updated to reflect closed=false default on the 'closed' query parameter - New endpoint: Added get-batch-prices-history.md (POST /batch-prices-history) - TARGET.md: Added new get-batch-prices-history.md URL
This commit is contained in:
@@ -1,4 +1,4 @@
|
||||
> ## Documentation Index
|
||||
< > ## Documentation Index
|
||||
> Fetch the complete documentation index at: https://docs.polymarket.com/llms.txt
|
||||
> Use this file to discover all available pages before exploring further.
|
||||
|
||||
@@ -6,6 +6,10 @@
|
||||
|
||||
> Welcome to the Polymarket Changelog. Here you will find any important changes to Polymarket, including but not limited to CLOB, API, UI and Mobile Applications.
|
||||
|
||||
<Update label="Apr 9, 2026" description="GET /markets: closed defaults to false">
|
||||
* **`closed` default change**: The `closed` query parameter on `GET /markets` now defaults to `false`. Closed markets are excluded from results unless you explicitly pass `closed=true`.
|
||||
</Update>
|
||||
|
||||
<Update label="Mar 31, 2026" description="REST API Fee Fields Update">
|
||||
* **Fee calculation source**: Fees should now be calculated using the `feeSchedule` object within a market.
|
||||
</Update>
|
||||
@@ -108,7 +112,7 @@
|
||||
</Update>
|
||||
|
||||
<Update label="July 23, 2025" description="Get Book(s) update">
|
||||
* We’re adding new fields to the `get-book` and `get-books` CLOB endpoints to include key market metadata that previously required separate queries.
|
||||
* We're adding new fields to the `get-book` and `get-books` CLOB endpoints to include key market metadata that previously required separate queries.
|
||||
* `min_order_size`
|
||||
* type: string
|
||||
* description: Minimum price increment.
|
||||
@@ -121,7 +125,7 @@
|
||||
</Update>
|
||||
|
||||
<Update label="June 3, 2025" description="New Batch Orders Endpoint">
|
||||
* We’re excited to roll out a highly requested feature: **order batching**. With this new endpoint, users can now submit up to five trades in a single request. To help you get started, we’ve included sample code demonstrating how to use it. Please see [Create Orders](/trading/orders/create) for more details.
|
||||
* We're excited to roll out a highly requested feature: **order batching**. With this new endpoint, users can now submit up to five trades in a single request. To help you get started, we've included sample code demonstrating how to use it. Please see [Create Orders](/trading/orders/create) for more details.
|
||||
</Update>
|
||||
|
||||
<Update label="June 3, 2025" description="Change to /data/trades">
|
||||
@@ -136,7 +140,7 @@
|
||||
</Update>
|
||||
|
||||
<Update label="May 28, 2025" description="New FAK Order Type">
|
||||
We’re excited to introduce a new order type soon to be available to all users: Fill and Kill (FAK). FAK orders behave similarly to the well-known Fill or Kill (FOK) orders, but with a key difference:
|
||||
We're excited to introduce a new order type soon to be available to all users: Fill and Kill (FAK). FAK orders behave similarly to the well-known Fill or Kill (FOK) orders, but with a key difference:
|
||||
|
||||
* FAK will fill as many shares as possible immediately at your specified price, and any remaining unfilled portion will be canceled.
|
||||
* Unlike FOK, which requires the entire order to fill instantly or be canceled, FAK is more flexible and aims to capture partial fills if possible.
|
||||
@@ -155,5 +159,4 @@
|
||||
* DELETE /order - 3000 every 10 minutes (5/s) - Throttle requests over the maximum configured rate
|
||||
</Update>
|
||||
|
||||
|
||||
Built with [Mintlify](https://mintlify.com).
|
||||
|
||||
Reference in New Issue
Block a user