Private Sector API Codesign PART III Panel discussion
summary
Panelists debate practical fixes: prefer consumer‑oriented APIs, keep multiple versions live during migrations, and email or portal notifications for deprecation; many public bodies still use heavyweight onboarding (X‑Road/AXRoad) so small users can’t join. Tooling discussed includes OpenAPI, AsyncAPI, GraphQL, and messaging (MQTT/gRPC); security relies on multi‑layer controls (API Gateway/API Connect, Ping, OpenID Connect) because JWT alone is insufficient. Marketplaces and smart data models exist as prototypes but business onboarding, semantic matching, and governance remain unsolved.
AI-written summary · about
chapters (9)
- 0:00Panel discussion intro
- 1:27Panelist intros and context
- 7:11API lifecycle and versioning
- 20:51Microservices impact on APIs
- 28:14API discoverability and catalogs
- 42:47API standardization and interoperability
- 55:56API tech and protocol choices
- 1:06:32API security best practices
- 1:21:20Closing remarks
related talks
29mAdapting to an API Enabled World (Panel Debate)
52mDiscussion: Digital coordination through APIs
50mPanel: We Have APIs, Now What?
27mAPI Design in Fintech: Challenges and Opportunities for next gen APIs
15mThe global trend of platformication
31mThe API in 2017
15mAPI Portals Reimagined: Past, Present, and Future Trends
48mAPI Security for Enterprises fireside chat