Automatically pay to have unfavourable reviews cleaned up, warnings that bad reviews will start to bubble up when payments aren't met etc.
Introducing Yelp's GraphQL API
11–20 of 54 posts
Re: Introducing Yelp's GraphQL API
#12Nice to see some technical leadership from Yelp. A tight partnership with 3rd party developers may be a nice way to go up against Google My Business and Bing Places. If anyone from Yelp engineering is reading this, I'd love to see a major player get behind some standard for uniquely identifying places on which we could join public and private place-based datasets. I like mapcodes: http://www.mapcode.com/
Take a look at Mapzen's gazetteer project "Whose on First". It aims to generate a unique identifier (and store with it concordances for other venue IDs, opening hours, images, etc.) for every venue on earth and is designed to handle situations where a business is started, changes location, or closes.
https://whosonfirst.mapzen.com/
(Disclaimer: I work for Mapzen)
Re: Introducing Yelp's GraphQL API
#13Is it possible to do more complex requests in GraphQL, like getting the favorite venues of people that favored "Garaje" or is it left to the API provider?
Not really. GraphQL mostly provides an alternative to REST when you want to select specific fields and traverse down into relationships with a single query. The closest you could get is the users who rated the business: business(id: "garaje-san-francisco") { reviewers { rating user { name } } } If Yelp wanted to enable that use case, they would add a field to Business like `related_businesses` like: business(id: "gar…
business(id: "garaje-san-francisco") {
reviewers {
rating
user {
name
favorited_businesses {
id
name
}
}
}
}Re: Introducing Yelp's GraphQL API
#14Going to sign up for the beta program. BTW, if you're in the SF area, definitely try Garaje. One of the best tacos and beers around.
Re: Introducing Yelp's GraphQL API
#15Nice to see some technical leadership from Yelp. A tight partnership with 3rd party developers may be a nice way to go up against Google My Business and Bing Places. If anyone from Yelp engineering is reading this, I'd love to see a major player get behind some standard for uniquely identifying places on which we could join public and private place-based datasets. I like mapcodes: http://www.mapcode.com/
Mapcode doesn't identify a place/business/venue, it identifies a location on earth. If the building moves or a business changes offices then the Mapcode changes, too. Take a look at Mapzen's gazetteer project "Whose on First". It aims to generate a unique identifier (and store with it concordances for other venue IDs, opening hours, images, etc.) for every venue on earth and is designed to handle situations where a b…
Re: Introducing Yelp's GraphQL API
#16Re: Introducing Yelp's GraphQL API
#17Nooooooooooo! Don't choose my favorite Taco spot as your sample query. The line is already too long.
Re: Introducing Yelp's GraphQL API
#18Nice to see some technical leadership from Yelp. A tight partnership with 3rd party developers may be a nice way to go up against Google My Business and Bing Places. If anyone from Yelp engineering is reading this, I'd love to see a major player get behind some standard for uniquely identifying places on which we could join public and private place-based datasets. I like mapcodes: http://www.mapcode.com/
Re: Introducing Yelp's GraphQL API
#19Re: Introducing Yelp's GraphQL API
#20Not sure if anyone at Yelp reads HN but looks like a bunch of the sample queries are broken. I'm not familar enough with GraphQL on how to fix them. https://www.yelp.com/developers/graphql/query/reviews