Fork me on GitHub

API Evangelist Blog

I Always Want To See the Data Behind, And So Does Plot.ly

Posted on

I don’t have a love of infographics, mostly because they more graphic, than info, and I’ve stated before that all infographics should have the data behind them. I’ve been working with data of over 20 years, I thoroughly believe in its importance when used right, but it seriously pisses me off when it is distorted in support of any argument—whether I agree with the argument or not. This sentiment is shared by a startup I was introduced this last week, called Plot.ly. I had a great conversation Nolan Browne the co-founder & chief business officer at Plot.ly, and he conveyed......read more.



API Service Accord

Posted on

Building off a conversation I had with a fellow evangelist in the federal government today, regarding API service level agreements (SLA), I wanted to talk through some thoughts I’m having about a couple of key API building blocks. Reflecting what I see across the API space, API terms of service (TOS) are the legal agreement that API consumers agree to before using an API resource. API best practices, tends to reflect what the API TOS lays out, but are delivered in plain english, avoiding the legalese of the standard TOS. When these two building blocks (terms of service, best practices)......read more.



The Power Of Designing And Deploying API Driven Resources In Containers

Posted on

One of the transformative experiences of my career was when I worked for SAP, running SAP events as VP of Engineering at WebEvents Global. When I started, I was handed an architecture that was completely hosted in a hostage colocation facility, where I had no support. Long story short is, I was able to redefine my architecture using an API-centric approach, coupled with AWS EC2 and S3 APIs, I re-deployed infrastructure piece by piece into the cloud, exiting my restrictive environment, but then also giving me a newfound agility, and the ability to scale in new an exciting ways, that......read more.



The 15 Sessions At API Strategy And Practice in Amsterdam

Posted on

I am getting psyched going through the schedule lineup of 15 sessions at API Strategy & Practice in Amsterdam. In planning the session outline, Steve, Vanessa and I listened to what the #APIStrat audience asked for after New York and San Francisco, which was more of the deep technical, as well as a balance of the business and politics of APIs. I think our lineup delivers on this, which we've broken up into three tracks: API Provider Design and Development Service Descriptions Hypermedia APIs API Marketing & Developer Communities Hardware and Internet of Things (IOT) API By Industry Media, Music......read more.



API Management: Adding Reciprocity Building Blocks

Posted on

I’m adding a new grouping to my list of API management building blocks, called reciprocity. If you want to know what I mean by reciprocity check out my earlier post From ETL to API Reciprocity, Looking at 20 Service Providers. As I was working with Nimble the CRM system last night, and I was planning out some workflows associated with keeping contact data up to date, and noticed that Nimble provides access to Zapier automation tools directly from their interface, using an iframe. Providing access to API automation tools for your developers, and end-users, is an important piece of a......read more.



API Talent Agencies

Posted on

I am watching Airpair and Workmob step up to meet the demand for developer talent in the API space, and can’t help but selfishly want to see the same for API evangelism talent. Along with the growth of the API space, the need for quality API developer talent has grown exponentially. Airpair and Workmob have both identified this (obvious) need, and will do well, if they can truly qualify, organize and direct talent to where it is needed across the space. I would call Airpair and Workmob, API talent agencies, with a focus on development. I want to see the......read more.



Which Building Blocks Should I Use As Part Of My API Support Strategy

Posted on

I wish I had more time to take many of the questions I get behind the scenes via email and publish as stories, but with an insane inbox I only can make time for some of the more relevant ones. I had one from a couple weeks ago that I just got around to responding to, which had to do with which support building blocks should an API provider use. This particular question comes from Jamie Parkins (@jamieparkins) from JustGiving: In your experience of documented APIs, when you come across the need for help, do you find the simple Google......read more.



Common Building Blocks of Cloud APIs

Posted on

I’ve been profiling the API management space for almost four years now, and one of the things I keep track of is what some of the common building blocks of API management are. Recently I’ve pushed into other areas like API design, integration and into payment APIs, trying to understand what the common elements providers are using to meet developer needs. Usually I have to look through the sites of leading companies in the space, like the 38 payment API providers I’m tracking on to find all the building blocks that make up the space, but when it came to......read more.



Viewbook Uses Flickr API Design When Designing Their Own

Posted on

I am spending time getting to know the APIs coming out of the Netherlands, as we prepare for API Strategy & Practice in Amsterdam March 26-28th, and one API I was checking out is from the Portfolio platform Viewbook. Viewbook provides an API for users to add and manage their photos, building very attractive portfolios for photographers. What I thought was pretty cool when I was going through their API, was their re-use of the Flickr API design, rather than re-inventing their own. Viewbook is a great argument why we need API Commons, and a central, sensibly licensed place to......read more.



Expanding An API Designers Horizon Using Apiary

Posted on

I spent some time developing a hello world product API with Blueprint, RAML And Swagger this last week, and along the way I had several experiences that I think are influential in the API design process. One of these was while I was designing my product API using Apiary.io. After I had gotten to a certain point in my design, and I wanted to see it in action, so I clicked on the preview button. A panel slid out showing me the interactive documentation my developers will see when it is published, and potentially see how it will work with......read more.



Google+