# spicedb


12/28/2021, 3:59 PM
Hey folks 👋🏻 One of the questions I had written down and meant to ask a while ago was expectations around ordering of results in LookUp / Expand API calls. As you note in the blog post, filtering is mostly used in index-like pages that list authorized resources. Such pages also tend to have various ordering criterias for the list rendered to the user. Some examples: - github's user repo page: - githubs organization repo page: Im wondering: - are there any ordering guarantees in Lookup/Expand API results? - how can an application order by other criterials without loading the full result set in memory?