|
|
|
|
|
by mgkimsal
3999 days ago
|
|
Maybe I'm too literal, or just... can't get past "terms of service", but... Yelp TOS: https://www.yelp.com/developers/api_terms "You agree that you will not, and will not assist or enable others to: cache, record, pre-fetch, or otherwise store any portion of the Yelp Content, or attempt or provide a means to execute any "bulk download" operations, other than storing Yelp business IDs which you may use solely for back-end matching purposes;" It looks like you're storing Yelp Content. Or maybe reviews aren't "Yelp Content" specifically? Or did you get a written waiver for this service? Or does no one ever give a toss about these TOS, and just complain on twitter when they get API access revoked? |
|
"The API is made available by Yelp Inc. ("Yelp") to enable you to access valuable local information and present Yelp Deals or Yelp Certificates on your website or mobile properties, including mobile apps ("Your Site") that encourages the visitors to Your Site (the "Users") to purchase certain Yelp Deals or Yelp Certificates (collectively "Yelp Voucher(s)") by directing them to Yelp's website or mobile properties, including mobile apps ("Yelp site")."
The entire purpose of the Yelp API is explicitly to get you to direct people to their site and/or to sell Yelp Deals.
Do people really not read these TOS before launching services, or do they think they can skate around the edges until they're big enough to get noticed/acquired before the API police cut off access?