Posted on 06-23-2011
This is one story I'm sure I will be telling over and over. Its about providing self-service registration to your API, and access to your documentation. I'm working my way through 78 travel APIs right now, reviewing each of them for a series of travel industry API stories. I'm only halfway through, and about 25% of them require me to email them or submit a contact form to get access to their API. I can understand doing this if your goal is to only work with partners and vendors, but all of these APIs came from the ProgrammableWeb API directory. So I assume your goal is to target a wider public audience. Here is how your approach is hurting you:
- As a developer I need instant gratification. I need to make sure your API has what I need. I need to quickly get at your documentation, see your endpoints, and potentially be able to grab a code sample and see some results. If you can't provide this for me, someone else will.
- As an API blogger and writer I need immediate access. If I'm going to include you in my story for the travel industry APIs, and showcase what you offer. I need access, without waiting or talking to you, to see the value you deliver, and where you fit in.
comments powered by Disqus
Winning in the API Economy
|Download as PDF|
Latest Blog Posts
- Adding The OpenEd API To The API Commons
- PR People For APIs
- I Will Be At API Days in Paris This Week, Will You Be There?
- Government Services Schemas With JSON-LD
- University of California Student Senate Submits Bill Stating Student Information Systems Must Have API
- Generating The Utility APIs I Need For Each Developer Portal
- An API For Your Github GeoJSON Stores
- Server Side API Templates On AWS Cloud Formation And OpenShift
- Hypermedia In The Wild: Amazon AppStream API
- API Search Endpoint Using Solr