Open TheTechArch opened 6 months ago
Proposed
There are several patterns on API design we might want to have a common decision on
Should we name API based on consumer of those API. Like ServiceOwnerRoles, GetDataServiceOwner,
How should we standardize for returning error codes from API
How should we setup products
Should we use O-Data in filtering?
What becomes easier or more difficult to do because of this change?
Status
Proposed
Context
There are several patterns on API design we might want to have a common decision on
Decision
Naming of API based on consumer of the API
Should we name API based on consumer of those API. Like ServiceOwnerRoles, GetDataServiceOwner,
Error codes
How should we standardize for returning error codes from API
APIM Products
How should we setup products
O data filtering
Should we use O-Data in filtering?
Consequences