Mufaddal Khambaty, Pax8, Senior PM, Integrations & AI
Many platforms start their API journey by issuing simple API keys, but quickly run into security and visibility challenges, especially when third-party developers enter the mix. This session details Pax8's evolution from insecure, direct API key usage to building a sophisticated, secure, and scalable 'Integrations Hub.' We'll share our real-world experience tackling the initial problem: how to allow third-party vendors to access customer data via APIs without compromising security or losing track of who was making calls.
Developers don’t want to read your API documentation. Yet too often, teams still rely on static docs, outdated Postman collections. In modern, fast-moving environments, that just doesn’t cut it.
This talk explores the shift from documentation-as-text to documentation-as-experience. We’ll cover the pitfalls of traditional API docs, and walk through practical, developer-friendly alternatives—like live sandboxes, executable notebooks, embedded tests, and self-validating examples that evolve alongside your code. You’ll learn how to make your API docs dynamic, interactive, and accurate by design—not after the fact.
Whether you’re building a public developer platform or internal APIs, this session will give you real strategies to reduce integration friction, cut support load, and create documentation that developers actually want to use.
Developers don’t want to read your API documentation. Yet too often, teams still rely on static docs, outdated Postman collections. In modern, fast-moving environments, that just doesn’t cut it.
This talk explores the shift from documentation-as-text to documentation-as-experience. We’ll cover the pitfalls of traditional API docs, and walk through practical, developer-friendly alternatives—like live sandboxes, executable notebooks, embedded tests, and self-validating examples that evolve alongside your code. You’ll learn how to make your API docs dynamic, interactive, and accurate by design—not after the fact.
Whether you’re building a public developer platform or internal APIs, this session will give you real strategies to reduce integration friction, cut support load, and create documentation that developers actually want to use.
Mufaddal Khambaty, Pax8, Senior PM, Integrations & AI
Many platforms start their API journey by issuing simple API keys, but quickly run into security and visibility challenges, especially when third-party developers enter the mix. This session details Pax8's evolution from insecure, direct API key usage to building a sophisticated, secure, and scalable 'Integrations Hub.' We'll share our real-world experience tackling the initial problem: how to allow third-party vendors to access customer data via APIs without compromising security or losing track of who was making calls.