> ## Documentation Index
> Fetch the complete documentation index at: https://docs.therundown.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Event history sportsbook limit

> affiliate_ids is required on event market history, and accepts 1 to 3 sportsbook ids.

`GET /api/v2/events/{eventID}/markets/history` requires `affiliate_ids`. Pass 1 to 3 sportsbook ids.

| Request | Result |
| - | - |
| `affiliate_ids=19` | History for that sportsbook |
| `affiliate_ids=19,23` | History for those two sportsbooks |
| `affiliate_ids=19,23,22` | History for those three sportsbooks |
| Omitted, blank, `0`, or a non-numeric id | HTTP 400: `affiliate_ids is required; pass 1 to 3 sportsbook ids` |
| Four or more distinct ids | HTTP 400: `affiliate_ids accepts at most 3 sportsbook ids per request` |

Repeated ids count once and do not increase the count. `affiliate_ids=0` is not a scores-only sentinel on this route. The request is rejected before any history read.

`market_ids` still defaults to `1,2,3` (maximum 12). `from` and `to` are optional RFC 3339 bounds. `limit` defaults to 1000 and accepts up to 5000.

Chart history (`GET /api/v2/events/{eventID}/markets/{marketID}/history`), opening lines, and closing lines still treat `affiliate_ids` as an optional filter. Examples such as `affiliate_ids=19,23` on those routes are unchanged. The [Historical Odds guide](/guides/historical-odds) example `affiliate_ids=19,23` on event market history is a valid two-book request.

WebSocket connection caps are documented on [Connection limits](/api-reference/v2/websocket-connection-limits).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.