[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"insight-x-api-openapi-2026-05-27-max-results-maximum-raised-from-100-to-1000-default-set-to":3},{"source":4,"alert":11},{"id":5,"displayName":6,"vendor":7,"kind":8,"apiType":9,"url":10},"x-api-openapi","X API","x","openapi-json","rest","https:\u002F\u002Fapi.x.com\u002F2\u002Fopenapi.json",{"id":12,"slug":13,"severity":14,"title":15,"summary":16,"detectedAt":17},"01KSN9GJC6NVRFNQA4WRMEB70N","2026-05-27-max-results-maximum-raised-from-100-to-1000-default-set-to","Breaking","max_results maximum raised from 100 to 1000, default set to 1000","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`.","2026-05-27T18:00:25.734Z"]