I absolutely wouldn't expect there to be notes against an API key.
Heck, in many companies I have encountered that they don't even know who is using API keys they've issued to third parties, especially over generations of systems. I am impressed that after getting email approval for an app a decade ago, Yelp still had contact details enough to let the O/P know!
None of that negates the issue of 4-days notice and Yelp shooting themselves in the foot by removing access to an app which redirects people to their website. But someone in executive management made a decision on the basis that they wanted revenue from the API overhead, wanted a slice of other people's pie and that's that.
To the O/Ps point about subscription, there was a UK food app which gave you restaurant food safety scores taken from the food safety agency "Scores on The Doors" it's gone now but I paid a few £ a year for it and never had an issue. If the Yelp pricing is sustainable at that level it's not a bad idea to pay for API access, Yelp has to pay for their servers and a portion of the API calls won't be converted to traffic. Who knows if Yelp still has a sustainable business? Maybe that API thing doesn't pay for itself? I don't know.
Maybe not for an API key, but for an account, you would think they would have some method of keeping notes. I've never worked for a company that had a concept of accounts, and teams of people that interfaced with accounts, without having a method of keeping notes about an account. That's just a basic necessity, especially when the accounts exchange money with the company, there's usually accounts that pay more than others that require special handling, which is usually documented in an account notes screen of some kind.
On the Yelp developer site you have an app profile where there is the name and description of the app. There is also a separate field for the URL of the app website, which I did have filled in. So, they have that at a minimum. If they didn't retain the records of the screenshots/communications that led to the original approval and raise of the API daily limit then that is poor recording keeping but understandable in a corporate environment after 10 years.
The API key usually has a contact email. After a year that contact email probably doesn’t work anymore, certainly for free tier.
Which underlines what I concluded long ago: the best and most durable form of identity on the internet is rooted in the ability to pay money. Any identity that is free to create is doomed.
Oh I completely agree - 4 days notice is _never_ OK. I get uncomfortable with 30 days notice because I've had the occasional vacation that long!
Ideally they'd have a notes field against developer apps and a robust process for recording this kind of thing - but I've worked for companies, so it doesn't surprise me at all that there's no good mechanism in place for that.
In real life, sometimes months isn't enough. On August 5, UPS will complete their API transition to OAuth based authorization after many months of process. Many of my customers haven't responded to my attempts to warn them about the change. I've resigned myself at this point to August 5 being a crazy day.
Yeah, you'd think so. But as many of us have learned, many companies can't and won't be considerate. Sorry that you got hit with it, but at least it's a quick and clean break.
Don't sweat the refunds too much (unless someone is being really rude about it). Apple certainly won't.
Btw, I'm pretty sure what happened was that this conversion was planned and carried out, but nobody was assigned the responsibility to tell developers. It was clearly done last minute using the most convenient form.
> Btw, I'm pretty sure what happened was that this conversion was planned and carried out, but nobody was assigned the responsibility to tell developers. It was clearly done last minute using the most convenient form.
Right, the biggest thing is a failure of communication. There should have been emails months ago, not 4-days (1 business day Friday->Monday) before.
There should have been an email months ago saying they were converting their API to be paid. Not a 4-day threat to shutoff your API key or pay-up. As I mentioned in my post, I was not aware that they were converting to a paid program and had received no prior emails.
Yes, I got that, but why should they bother? Your understanding is that you were business partners, while in fact, you were just lucky enough to get access to their service for some years.
If you had an actual contract, it would be a different story. Your product would still be not more than some UI to some walled garden, and nothing particularly valuable, but at least you would be officially permitted to do so.
So you basically sold something to Apple users that you don't actually own, and that is completely out of your control, and that was always in danger to just stop working suddenly.
And, on the other hand, I'm sure you've implemented a (for a hobby) decent app, and maybe you actually brought a handful of new visitors to them (which wouldn't have just used their website if your app wouldn't exist). But do you really think that at Yelp they are sitting there and just think how they can return the favor?
They basically think "well, that funny dude has now played enough". You never were a partner for them. Just what people call " useful idi*t" (sorry, but that's just the term ^^) at best. They haven't talked about you at their christmas party!
If you're up front and reasonable, you're more likely to convert developers to pay for the new API. If you do it last minute, not only can't developers make the switch in time, you've lost their trust, making it harder to convince developers to bother investing their time and resources.
Their business is completely independent from a funny guy who writes some iPhone app. They haven't lost anything in that story. If they need a new iPhone app, I'm sure they will find developers for that.
Regardless, even if it had been active for 10 months not 10 years, 4-days notice is unacceptable.