Agreeing on common standards for trust with APIs
summary
APIs often report misleading success: one case shows 5% of traffic returning 200 but failing because content isn’t validated, and gateways or APM logs can hide problems. Latency measured at the gateway differs from client experience — up to 2.5 seconds extra was observed — and a regulator’s time-to-first-byte metric can be gamed by immediate gateway bytes. Onboarding 38 regulated banks takes wildly different times (first 18 in one day, next 10 six weeks, last 10 four weeks). A proposed CASK score out of 10 blends pass rates, statistical smoothness and outlier rates to compare API quality.
AI-written summary · about
chapters (17)
- 0:00Introduction
- 2:50In Search of Schrodingers API
- 3:17Trading as Cat
- 4:28Common Issues
- 5:57Common Problems
- 7:29Spec Schemers
- 9:03Latency
- 9:36Time to First byte
- 12:54Why trust matters
- 15:28Common standards
- 18:20Mark your own homework
- 19:13directories
- 20:15wrapping up
- 23:02we are the essential linchpin
- 23:44api expert
- 24:25QA
- 25:08API metrics
related talks
54mFive-step plan for securing your APIs
25mBoost API Success: Key to Transparency & Accountability
36mOne to millions - opportunities and challenges in scaling APIs.
23mFrom API Intelligence to API Governance [...]
21mAPI Design in FinTech: Challenges and Opportunities for next-gen APIs.
24mThe Broken Promise of API Management in Open Banking
36m10 Things You Hate About Your API Gateway
21mUnlocking Data Silos Securely: Standards‑Based APIs for Regulated Sectors