The API in 2017
summary
Government regulation is pushing banks to open APIs and a payments platform claims developer-first design reduces integration pain by shipping SDKs, tokenization and customer-led features. Advice includes using Swagger to auto-generate up‑to‑date docs, enforcing rate limits, and keeping sensitive data off‑site via tokenization. Teams adopt inner‑sourcing on enterprise GitHub, migrate legacy Java/C++ to Node, and prefer purpose‑built endpoints; real examples: Singapore’s Smart Nation, a proposed unified “my info” ID, and Firebase reverting to XMPP.
AI-written summary · about
chapters (10)
- 0:00APIs and their ubiquity
- 4:16Braintree’s developer-first origins
- 7:47API integration pain points
- 11:17API architecture evolution
- 14:49Building APIs for purpose
- 19:25Future of APIs
- 22:13Developer programs
- 25:01Open source tools
- 27:50Prioritizing API features
- 29:58Feedback and great APIs
related talks
01h 03mImplementing APIs in 2019
23mWhat Makes an Agile API?
25mOpen banking - From Efficiencies to Externalities!
01h 29mPrivate Sector API Codesign PART III Panel discussion
29mDriving innovation through External APIs without putting your business
26mReimagining the Banking Core: APIs as the Digital Fabric of Transformation
21mUnlocking Data Silos Securely: Standards‑Based APIs for Regulated Sectors
18mSecure your Apps and APIs with strong authentication and Adaptive Access.