The standardization of APIs will shape the overall experience producing and consuming APIs. The number of and types of standardizations will shape the design of the API itself, as well as the onboarding, authentication, and other downstream aspects of consuming an API by developers. The experience of teams producing APIs will be streamlined with standards and help immediately reduce friction and save time for consumers of an API. Internet and industry standards will help align enterprise resources and capabilities with what is expected by consumers of APIs, ensuring that interfaces already speak the language of a busienss sector, or the World Wide Web.
Standardization
Policies
Naming Conventions (Design)
Require that every API follows a single, documented set of naming conventions for resources, fields, parameters, and enums, so a developer who learns one of our APIs already understands the next. E...
Open Standards Adopted
Require that APIs are defined and delivered using open standards such as OpenAPI, AsyncAPI, and JSON Schema rather than proprietary formats. Open specifications lower the cost of adoption, enable i...
Strategies
APIs Prefer Open Standards and Open Source
Every proprietary shortcut an API takes becomes a tax paid by everyone downstream. I want API operations to prefer open standards like OpenAPI, AsyncAPI, and JSON Schema, and to lean on open source...
