As the name suggests, these APIs are more generic in nature and meant to satisfy not just one but multiple use cases and scenarios. They are not bound (coupled) to a specific user journey or system of engagement (for example, a mobile app), and are therefore ideal to be reused enterprise-wide.
Because of this, guiding principles and governance for designing such APIs tend to be more rigorous. One obvious example is how data objects are modeled with JSON objects should be defined in such APIs. Normalized data structures that are not coupled to any specific backend or frontend application should be used. Otherwise, there is a risk that the API will have to change along with changes made in backend and frontend systems, which ...
