Thank you for the comment and welcome to the disucssion.

I put that REST call as example. There may be scenarios like below.

A Typical ecommerce platofrm which fetches nutrition details for the ordered items in the list. for example customer can order 23234, 43234, 234234, 23432

then you need to get the nutrition details for those items only.

In that scenario, you can't use offset limit concept. with REST, you need to go with GET query or POST body.

Lets another scenario where you need to cross cehck 100 items which can be ordered bu customer or not.

If you have a single endpoint with only one item number then you have to call 100 times which is really not efficent move. also using limit offset also not going to work here. In those scenarios GET with query parameters or POST with body will work in normal REST.

That said, if the number of IDs gets too large (e.g., 1000+), pagination or chunking might be preferable to avoid hitting URL length limits or performance bottlenecks.