Trading fee legs say when they are null, and a scheduled change never has a null leg
The taker and maker legs of trading_fees are null in a few documented cases, and a scheduled_change now types its legs, and itself when present, as never null.
trading_fees.taker and trading_fees.maker on GET /v1/markets/{market_id} are JSON null, never omitted, when no fee model can be stated for that side, and their descriptions now say exactly when, by availability. published never has a null leg, so taker.rate is safe to read once availability is published. partial has one where the venue does not let us state it: Limitless's taker, a Polymarket maker whose market record does not say only takers pay, and both legs when a record omits its fee parameters. SX Bet is account_specific with both legs null, and unavailable always has both null. Nothing about the responses changed; the spec was only vague.
What did change is the generated types for scheduled_change. Its legs are never null, because a change is reported only when both legs can be stated, and the object itself is omitted rather than null when there is none. TypeScript, Python and Go now type them that way, so tradingFees.scheduledChange.taker.rate compiles under strict without a null check. The legs of trading_fees itself stay nullable, since they are null in the cases above.