Skip to Content
PredictorSDK

Game-line rule rows are now opt-in with include_rules

A game line always carries settlement_equivalence; its rule_comparisons rows now come only with include_rules=true, which makes default responses about 60% smaller.

Fix

Every moneyline, spread and total recently started carrying rule_comparisons, the three rows (tie, overtime, push) that say how each venue settles a tie, overtime and a line that lands exactly. They turned out to be about 60% of every football event's size, and the football period lines added the same day multiplied the markets they ride on. A page of 100 events with every submarket reached about 11 MB, its first byte took anywhere from 1.3 to 9.4 seconds, and some requests ran into the API's nine-second limit and got a 503 or an empty 502 instead of data. GET /v1/matching-markets/sports and GET /v1/matching-markets/sports/lookup now take include_rules (boolean, default false). Without it a game line still carries settlement_equivalence, the verdict, and leaves out the rows behind it; with include_rules=true the response is exactly what it was before this change. In a test shaped like production, default responses are about 60% smaller. If you read rule_comparisons on a moneyline, spread or total, add include_rules=true, ideally on a lookup or a small page. Player props are not affected: they always carry their nine rows. A cursor works with or without the flag, because it changes what each event lists and never which events come back. The regenerated SDKs add includeRules (TypeScript), include_rules (Python) and IncludeRules (Go). Read game-line rules.