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
- Where Do We Start With APIs At The University of Oklahoma?
- What I Would Look For When Hiring a Modern API Developer?
- The U.S. International Trade Commission Includes APIs In Latest Report
- Thank You @3Scale For Investing In The Community With @APIStrat
- Introducing API.Report, A Community API News Site
- Extract Knowledge From Audio And Video Using The Clarify API
- My API 101 Workshop At @APIStrat In Chicago Next Week
- Some Advice For The Enterprise When Beginning Your API Journey
- Machine Readable API Definition Format Swagger Matures to 2.0
- How Do We Continue Moving Green Button Data And APIs Forward?
- Beyond Public APIs In Government: Internal Access to Resources
- Can You Show Me The ROI On All Of This API Stuff Before We Commit
- In The Future APIs Will Be Default For All Cities
- No Public APIs Are Not Going Away Just Cause A Few BigCos Fumble At It
- Internal API Search Engine For Everyone At Your Company (Not Just Developers)
- If You Need Assistance With Your Healthcare API Strategy I Have The Person
- Explaining APIs To Senior Leadership: Access To Company Resources Without The IT Hassle
- A Conversation With @ijroth, @dorkitude, @antonyfalco, and @medjawii In The Next Generation API Stack Panel @APIStrat
- API Evangelist Thoughts On The Right To An API Key And Algorithmic Organizing
- Explaining APIs To Your Senior Leadership
- An API Evangelism Strategy To Map The Global Family Tree
- Thank You For Your API Evangelist Blog(s)
- Video From The Hypermedia Panel At API-Craft In Detroit Last Month
- Please Open Source Your API Before Shutting It Down
- Explaining My Work Around APIs In Higher Education To Institutions