Even Billion Dollar Brooklyn Companies Aren’t Perfect

Something that we always harp on is the lack of testing people are doing for APIs. Specifically in regards to the API’s response. We have spoken with hundreds of companies and each time are amazed to hear how few have systems in place. The best case scenario is that they are monitoring the latency of their endpoints, but that’s […]

API Testing Still In Its Infancy

Note: This post was originally a guest post for the readme.io blog. Reprinted here. Are you testing your APIs? I ask people this question daily. Some say they do, but it’s not many. The most conscientious boast of their unit tests and an occasional smoke test, which is progress, but when compared to the rigor we regularly […]

Can’t a Developer Do That?

Can’t a Developer Do That? This is a common question we hear when talking to people about API Fortress. It’s a simple question, but unfortunately the answer isn’t so simple. Yes they can. Oh, actually that was simple. Except when you dig deeper you see the much bigger problem. Technically, yes a developer can create their own […]

Out With the Old, In With Three New

ESPN announced they are shutting down their public API. This brought sadness to the API Fortress team as the ESPN API was always one of our favorite demonstration APIs, but not for the reason you may be thinking. It was our most active test of the notification system. The ESPN public API had problems on a […]

API Problems Confessional – Episode 2

A friend of mine, staring at a nearly empty glass of beer last night, complained about his latest disastrous API work. We have to build software off an API and the client provided a document with ‘all the necessary information’to use it. What they called documentation was a pile of random data, filled with overly […]