Focusing on Problems When Defining a New API
I am working on version 2.0 of the content API I am using as part of my work across Postman Open Technologies. It is a little meta, but I have an API for managing the content I produce and then distribute across the blog posts, videos, and books I am producing. I am using the API to help standardize and power the storytelling across my own work, but continue leveraging to do the same across my team. I’ve been using a half-baked version 1.0 of my API to guide my work for the rest of the year, but I am looking to continue adopting our internal approach to API-first at Postman as part of how I work externally as my team’s operational, demo, workshop, and community APIs. To kick off this effort I am sitting down with Bruno Pedro (@bpedro), the product manager helping lead API-first within Postman, as well as our public API strategy, and beginning to walk through his API playbook.