I’ll add that is a big deal for any of your high $$ clients who are big, monitor many transactions and consequently have queries that regularly return more than 1000 results. I get having a limit on LIMIT of 1000, that’s fine, but a lot of us will need to go paginate past the 1000th record. (I noticed that this doesn’t seem to work yet, though OFFSET is a legit keyword)
While we’re making pagination requests, I’ll throw in my vote for using OFFSET rather than pagination tokens. The former has more uses than the later and is sometimes easier to digest. Also, I’m noticing that on a the returned item count and total count (including items outside the offset/limit) are not included in the json response body. IMHO, those make life MUCH better for an API consumer. They make it so you don’t have to query past the last record to know that you’ve queried to the end.