Blog

15 lessons from 15 years in APIs

Originally published on LinkedIn, January 20, 2025.

Treat APIs as products. Design-first, not code-first. The dev/architect/PM lines are blurring. Fifteen lessons from fifteen years in APIs.

15 things I learned from 15 years in APIs:

  1. Treat APIs as Products.

  2. Do design-first, not code-first.

  3. You need the skills of API & Platform Product Managers and Architects.

  4. Devs<>Architects<>PMs, lines are blurring. There will be a lot of overlap.

  5. You must do customer discovery for APIs, do not “build it and they will come”.

  6. Stay close to customers - the whole team should participate in support and sales calls.

  7. API delivery should be disciplined and have standards, specs, tools, and metrics. You should run automated tests in every step of the API Lifecycle.

  8. Drive everything through artifacts such as schemas, and API Description docs. Check them into version control and reuse them for DRYness and accuracy in configurations.

  9. Work as one delivery team, with Architects, PMs, Engineers, QA, Tech Writers, and even Sales & Marketing - have common goals for all.

  10. Use AI to help you with design, consistency, Codegen, tests, and speeding things up in general - AI will touch every aspect of your work, and OpenAPI is best generated from LLMs.

  11. Good UX/DX is worth the cost and effort, for humans as well as Agents. It can be your differentiator.

  12. Speaking of onboarding, have distinct, clear landing pages per use case. Measure and learn from them.

  13. PLG is a great fit for APIs - in fact, it’s the OG use case and the only way to sell.

  14. AI Agents are the future of API consumption - prepare for it.

  15. Transition to outcome-based pricing, not per-seat.

Which one is your favorite? What have you learned? What would you add? ⬇️