I've read the API and noticed that you do not provide IDs for the top-
level categories (Arts & Entertainment, Food, etc.) ...
Unless this is caused by technical difficulties, I would see this as
something that could be considered essential... providing these Ids in
the Category Search endpoint (
https://api.foursquare.com/v2/venues/
categories), in conjunction with the Venue Search endpoint (https://
api.foursquare.com/v2/venues/search), would seem to be a good idea,
when wanting to perform a Search of Venues by Category...
Ideally, even if you didn't provided top-level category ids, it would
be a good idea to pass in an array of CategoryIds to the Venue Search
endpoint, along with the 6 other public ones you provide now (ll,
llAcc, alt, altAcc, query, limit). This would allow us to return more
relevant search results, when searching for venues, and ultimately
less requests to your system, as the data we get would be better
shaped.
Currently, to build a list of 100 "food-type" venues relative to a
given set of coordinates, a user would have to (a) perform a search,
parse through the JSON results (which gives us < 100 results), and
then make further requests to get the 100 desired results... or (b)
increase the search limit to a much larger number, to hopefully
guarantee the 100 results that would match the desired CategoryId.
By providing this parameter in the endpoint, a user can ask for 100
"food-type" results and get them, ignoring venues that weren't
desired. One would think this is less taxing on both the client and
your servers (I'm sure you get the idea)...
Looking forward to your response, and you guys have done a great job!