The paths for your API as defined by OpenAPI are how you guide your consumers into your wholesale outlets to purchase all of your digital resources and capabilities. These paths are baked into desktop, web, mobile, device, and artificial intelligence applications, and become how you distribute digital products to end-users.
Having a strategy for how you name and organize your paths is important to reining in the sprawl of your API operations and application distribution channels. All of the words used in the paths of your API should be part of a deliberate and well-known vocabulary of nouns and verbs that are intelligently used by product and engineering teams with delivering APIs.
API paths should be readable and intuitive, even for non-developers. Your API paths should be well organized and evolvable as your business changes. Think of all the work you have put into the paths for web properties over the years, and consider how much work you have to do the same for your API paths. Modern HTTP APIs are just the next evolution of the web and reflect the scope and efficiency of your modern digital distribution channels.