Stack Apps is a question and answer site for apps, scripts, and development with the Stack Exchange API. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

What is the current reasoning for the badge routes not being paged? Badges (/tags) is probably the current longest route, and it is annoying that this route isn't paginated, but stackauth/sites is. Should it not be the other way around (unless I am missing something obvious)?

share|improve this question
up vote 1 down vote accepted

They were't paginated due to their essentially static nature.

This has since been determined to be a mistake, they're slated to be redone in a subsequent API version.

share|improve this answer
great, something to look forward to recoding :/ And the sites method isn't [roughly] equally static? – Jonathan. Mar 15 '11 at 0:08
@Jonathan: The sites method is obviously not static by nature (in the sense that it changes frequently). – Nathan Osman Mar 20 '11 at 6:44
Sites route is quite static, we are told it must be called no more than once a day at minimum, and compared to questions it's very static. But there is no case when you'd only download the first page of sites. – Jonathan. Mar 20 '11 at 9:20

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .