Authenticating.com API Experience Review
Bill Doerrfeld | May 10, 2020
I was recently tasked to audit the Developer Experience of the Authenticating.com APIs, a suite of low code APIs for developers to add trust and safety to their applications.
More Info: Developer Experience Reviews
My goal was to provide actionable insights to improve the DX and marketability of the service. The project culminated in a 14 page report and 1-1 consultation.
Overall, though I found developer experience hangups with Authenticating.com, the core service has strong market potential.
Certain API design incongruities were found while testing. Certain API calls didn't match documentation in practice. Error handling was inconsistent. No sandbox existed, no developer account dashboard was live, and doc design looked like a basic template. I also found endpoint naming inconsistencies, and other style issues.
My recommendations included standardizing API design and style elements, and improving documentation to be more explicit for more use cases and circumstances. I recommended adding an OpenAPI specification as a source of truth, and a sandbox for API testing.
As the API landscape grows, developer experience is becoming more of a top concern, especially for newcomers trying to get a foothold in the market. I really enjoyed this project and hope to do more developer experience reviews in the future!
Other Blog Posts
I'll be writing a weekly series for The New Stack this fall covering Kubernetes, cloud native, and everything happening on the road to KubeCon in November.
I'm teaming up with Dan Barahona and AI Security University to put together the MCP Security Conference, a free half-day virtual event dedicated to MCP security .
My latest DirectorPlus edition interviews Shopify's head of engineering, Farhan Thawar, on their unique internal engineering culture.
Neoclouds promise cheaper GPUs and AI-optimized infrastructure, but can they really challenge hyperscalers? My feature on InfoWorld explores their advantages, risks, and likely role in AI compute.
My latest for LeadDev interviews IBM's Neel Sundaresan on how to prevent a decades-old issue in software engineering.
The latest advancement in identity and access management (IAM) is something called zero standing privilege. It's a response to new agentic AI risks.
Big surprise: it's way easier to generate new code with AI than to reuse old code. But what are the long-term effects?
Agentic coding tools have become the default. "When we've taken that away accidentally from people, they scream."
My latest for LeadDev considers how engineering leaders should respond in the wake of uncertainty in the AI model market.
I'm working with Zuplo on some new content around their MCP Gateway release. First up: a deep comparison of MCP gateways on the market!
