I discussed this with @nicklewis and we decided that the v1/v2 endpoints should not support the paging query parameters.  This seemed like the easiest way to enforce and test that.

Also, I'm kind of of the opinion that it's not a good thing that we don't error if you pass unsupported query params in general; it means people can make a simple typo somewhere and end up being very confused about why things aren't behaving like they expect.

So... I guess the question is: do you feel so strongly about *not* enforcing the absence of these parameters that you think it's worth introducing a bunch of extra complexity to the tests?