Proto is a betting-product surface at /v1/proto, rather than a league ID. Its fixture reads require odds access and use the normal REST quota/rate-limit chain. Fixture listing accepts integer game_type, year, round, status, integer timestamp from/to (inclusive epoch milliseconds), league_id, cursor, and limit. Round listing accepts game_type, year, status, cursor, and limit. Both default to 25 items and cap at 200. Proto numeric statuses/types are provider codes; do not replace them with universal game-status strings. Malformed optional numeric filters can be ignored by the parser. Only mapped fixtures are returned by the canonical fixture reads. Multiple source fixture rows can collapse into one canonical game, with their markets merged. Zero/invalid odds are removed. For repeated selections, an active positive quote is preferred over a blocked one, then the freshest quote wins.

​
Market fields

Each market can include sequence, market_type, market_name, string line, single_bet, end_date, status, and odds. Selection rows can include index, name, numeric odds, bet_count, purchase_rate, blocked, and result. These are Proto fields; they do not use the general price_american/price_decimal projection or format query. Round metadata includes id, game_type, game_id, game_round, year, game_name, status, source update times, and available sales dates/totals, fixture counts, result counts, and finish/sync times. Preserve the timestamps’ declared type in the reference: source_created_at, source_updated_at, and sales/finish dates are integers; synced_at is a string when present.
Use the returned canonical ID and league to fetch the corresponding normal game, lineup, or match detail. An unmapped upstream Proto record is not a canonical API fixture.