Nothing on the interwebs is forever. Services start up and either become successful, get acquired or shut down. If they shut down they usually end up in TechCrunch’s deadpool. The same applies for APIs and when they finally go offline, they usually end up in the Programmable Web deadpool.
Yesterday I was running some tests on the latest pre-release version of Mapstraction, which still supported the Yahoo! Maps API and they were running without error all morning. Then they stopped. The API just wasn’t there anymore.
$ wget http://api.maps.yahoo.com/ajaxymap?v=3.8&appid=(redacted)
Resolving api.maps.yahoo.com... 220.127.116.11
Connecting to api.maps.yahoo.com|18.104.22.168|:80... connected.
HTTP request sent, awaiting response... 503 Service Unavailable
A quick look at the API’s home on the web at developer.yahoo.com/maps/ajax/ shows an update to the previous shutting down message, with developers now being redirected to developer.here.net, the home of Nokia’s new Here Maps API.
So whilst the demise of the Yahoo! Maps API in September of last year proved to be somewhat exaggerated, the plug has now been well and truly pulled.
I’ll always have a soft spot for the Yahoo! API; it was the first mapping API I really cut my teeth on and while things change on the interwebs on a daily basis I can’t help but feel sadly nostalgic.
This does mean that the next release of Mapstraction will no longer support the Yahoo! Maps API, though it will support Nokia Maps and Here Maps. My signed copy of Charles Freedman’s Yahoo! Maps Mashups will also continue to remain on my office bookshelf as a memento.