CODEWITHSUNDEEP
apifoursquare
wildehahn
wildehahn

Reputation: 1861

Foursquare venue added with api not showing up on userless search

I've added a foursquare venue via the api attached to my access token. I've included all the proper fields, name, city, ll, etc. and it shows up as the first result when I search for the venue based on the ll param when using my authenticated api. However, if I search with an api attached to another access token, or do a userless search, it doesn't show up in that result set. It will show up though if I add a query param and search for the name.

Am I missing something about how I am supposed to create the venue, like some sort of make_public flag? I'd like to be able to create a venue tagged with an ll and then have it show up when that same ll param is passed into any sort of api, authenticated and not. Is this possible?

Upvotes: 1

Views: 1524

Answers (1)

akdotcom
akdotcom

Reputation: 4687

Is this venue a "home" venue? If so, see http://blog.foursquare.com/2011/09/29/making-your-house-into-a-home/ which talks about some of obfuscating foursquare does around home venues which would explain your observed behavior

Update: Since the venue you added has 0 check-ins, it's considered a low-quality venue and is bypassed in favor of higher quality results that are nearby. The reason it's returned for the authoring user is because we consider it high-relevance for that user. All other users will probably need to specifically search for the venue before they will see it (as the venue acquires check-ins/activity, it may organically start appearing for query-less searches). For example, if I search for "library" at that location, I get your result back: https://developer.foursquare.com/docs/explore#req=venues/search%3Fll%3D37.7754738,-122.39986550000003%26query%3Dlibrary

Upvotes: 1

Related Questions