Platform API list endpoints now support ordering on fields other than ID
Change effective on 16 August 2013
List endpoints in the platform API (for example, GET /apps) now support ordering via the Range header. Each list endpoint will now respond with an Accept-Ranges header that indicates what fields it can be ordered on, and the name of one of those fields can then be used by crafting a request to that endpoint with a header like Range: name .. See ranges in the platform API reference for more details.
Furthermore, referring to the id field in a Range header as ids has been deprecated (please use the singular id), the API no longer returns a Prev-Range header, and ranges that include only an end bound without a start bound (e.g. Range: id ..123) are no longer supported.