Posted on 08-26-2014
My friend Mark Silverberg (@skram), pointed out a very cool API the other day, that geolocates zip codes, and appropriately named ZipLocate. What I really like about ZipLocate is that they do one thing, and they do it well. Don’t get me wrong I love me some AWS and Twilio, who have industrial grade APIs, but I also have a love for simple, lightweight APIs that focus on one thing.
Another interesting thing about ZipLocate is that it is always free, and never rate limited. He says that it is relatively cheap to host the API, because bandwidth usage is light, with all API calls are heavily cached. I like this type of micro service design--I want thousands more just like it.
What I also dig about ZipLocate is that if you “...don't trust the API to be around tomorrow? Host it yourself. Source code and data import scripts available on Github”. This is possible because the ZipLocate API is open source, and the data comes from the Census Bureau. This approach to developing dead simple APIs on top of government data is really important, and I personally feel that all 6,482 data sets across 22 federal agencies who have published their data.json file, should have APIs just like ZipLocate.
It looks like ZipLocate is a project developed by Nathan Cahill (@nathancahill). I like his style, and think his approach is simple, elegant, yet extremely powerful, and provides a blueprint that others can follow when designing, developing and deploying APIs built on top of public data.
comments powered by Disqus
Winning in the API Economy
|Download as PDF|
Latest Blog Posts
- Someone Please Build My Open, Interactive, Portable, And Visual API Documentation Toolkit
- Dwolla Using Slate For An Evolved API Documentation Experience
- Crazy Mess Of URLs Across 400 Of The APIs In My Stack
- Reworking My API 101 Content: Consuming APIs
- I Need Help To Make Sure The Dept. of Agriculture Leads With APIs In Their Parks and Recreation RFP
- What Is The Biggest Challenge For Fraud Detection API SiftScience?
- Reworking My API 101 Content: Providing APIs
- What I Spent Ada Lovelace Day Working On
- An Outside-In Approach To Jumpstarting An API Effort At The University of Oklahoma
- Exposing Dictionaries From My API Collections