Building APIs for Developers & Machines
summary
Claim: contract-driven development cuts integration friction by enforcing specs in CI, generating client/server artifacts, and running consumer tests (Pact) while lint/validate steps use Spectral and Apollo CLI for consistency. Tooling includes OpenAPI/Swagger, GraphQL Playground, gRPC Studio, Prism/WireMock for mocks and buf for proto checks. Atlassian integrates Confluence–MCP using a rich schema, uniform pagination, idempotency, caching, scoped OAuth and rate limits; result: faster codegen, trivial testing and predictable production behavior.
AI-written summary · about
chapters (9)
- 0:00Introduction
- 1:54API friction points
- 5:24Contract-driven lifecycle
- 8:33API design principles
- 13:48API paradigm matrix
- 19:04Atlassian API success
- 22:36Conclusion and API design best practices
- 23:18Q&A: MCP integration
- 24:22Q&A: API testing
related talks
47mContract-Driven API Development with OpenAPI Specification
40mAPI Lifecycle: Smarter Design and Governance With Open Tooling
26mAPI Governance: The Latest Trends Making Teams Love API Standardization.
49mBuilding Software Better: API Lifecycle Management for Developers
32mProject API Forge: Streamlining Dev-First API Lifecycle Management.
35mOpensource API Tools to agile your apifirst strategy.
54mSolving challenges in API Testing to achieve more agile development
48mContract Driven Development: The Death of Integration Hell