Okay, I switched to infinite scroll instead of pagination, that way I don’t have to know the total number of recipes I search would return. I just keep asking for more until there are no more left.

I have this already on my todo but unfortunately it is currently not that easy - or more so rather computationally expensive - to find out how many recipes would match in total after I found the requested amount. I will look into adding this, for now, maybe you just show a “next page” button? Also, looking at paging behavior in general, people tend to not look past the first page anyway so most of the effort must be put into the top search results. Also a good read is the first answer here: http://ux.stackexchange.com/questions/36394/when-is-it-better-to-paginate-and-not-to-paginate

Anyway I have it on my todo for the future 😃

Offset and number get me almost all the way there. The one thing that’s missing that I need the endpoint to return is the total number of recipes. I need the total number of recipes for any given complex search so that I can calculate how many pages to paginate through (number of pages = total number of recipes / recipes per page). Is this something you could add? This is different than the existing number attribute which maxes out at 100. I’m fine with only being able to get 100 recipes at a time, but I need to know: 100 of how many?

Hi,

The complex search endpoint has an offset and number parameter (https://market.mashape.com/spoonacular/recipe-food-nutrition#complex-recipe-search) which can be used for pagination already 😃