max_results maximum raised from 100 to 1000, default set to 1000
BreakingBreaking change
This is a breaking change — integrations that rely on the affected behaviour will need updates before the change rolls out.
What changed
The max_results query parameter schema has changed: its maximum was raised from 100 to 1000, and a default of 1000 was added. This is additive in the sense that larger page sizes are now permitted, but it is potentially breaking for clients that relied on the previous cap of 100 to limit response payload size — they may now receive up to 1000 results per page if they omit max_results or if server-side enforcement changed. The description also now documents pagination via pagination_token from meta.next_token.