APIs don’t just magically appear. Someone makes a decision. Whether it happens at a project/tactical level, or strategically, as a business-led initiative. We think ideas are better supported when they have legs. Like actual building blocks, so there’s no miscommunication when passing the baton.
Every API gets designed, but only so much of that API design gets executed. As an organization, you’re deciding if you want developers coding off of multi-versioned spreadsheets, or domain-driven design that builds out a global enterprise catalog for reuse, speedy governance, and innovation.
There are plenty of ways to build an API. Do you want developers handcrafting, using editors, and duplicating resource methods, or do you want to generate implementation details off of every detail you’ve captured in design, giving developers the exact artifacts they need for implementation?
APIs have to run somewhere. They need to be accessible, secure and performant. How do you know the version you’ve tested is what’s actually running? That design details are honored and monitored as the API executes? Do you leave it to manually deploying and configuring your runtime? Or do you automate the flow from design to build to runtime for successful APIs at scale?