With the up coming Fellowship One RESTful API we wanted to take the some time and look back on our other two APIs and reflect on what we intended them to be and what they actually became. We looked at the their interfaces, authentication, resources, versioning, protocols, logging mechanisms, “debuggability”, etc… What we found out was that in the world of “API” nothing ever ends up like you intend.
Fellowship One Data Exchange: A very powerful XML RPC API that was specifically designed to address massive data import and export needs. It’s ridged pinpoint interface allow users to build simple data presses, which move large amounts of data between disparate systems. A few years into the product’s life we introduced the ability to do synchronous transactions - a decision that completely changed many consumer’s usage patterns.
Here is the HTTP Header map for the upcoming Fellowship One RESTful API. Please comment / ask questions / make suggestions.
- 3rd Party App Showcase
March 22, 2013
- API Communication Value Changes
November 2, 2012
- API Enhancement: Create and Edit Groups!
August 13, 2012
- API Enhancement: Requirements Exposed
June 25, 2012
May 23, 2012