Is your feature request related to a problem? Please describe.
OData stands for Open Data Protocol, and it is a standardized protocol for creating and consuming RESTful APIs. OData is based on widely accepted web standards like HTTP, REST, and JSON, and it enables the creation of data APIs that can be easily consumed by a wide variety of client platforms, including web and mobile applications.
Describe the solution you'd like
Some of the benefits of using OData include:
Interoperability: OData allows data to be shared and consumed across different platforms and devices. This makes it easier for developers to create applications that can work with different data sources.
Standardization: OData provides a standard way of creating and consuming RESTful APIs, which means that developers can rely on consistent behavior across different implementations.
Queryability: OData supports rich query capabilities, including filtering, sorting, and pagination, which makes it easier to retrieve and work with large amounts of data.
Security: OData supports various authentication and authorization mechanisms, which makes it easier to secure data and control access to it.
Tooling: OData has a rich ecosystem of tools and libraries that make it easier to create, test, and consume OData APIs.
Additional context
I think one endpoint like getAll and getById can apply OData and back-office and both mobile can get what they really want.
Is your feature request related to a problem? Please describe. OData stands for Open Data Protocol, and it is a standardized protocol for creating and consuming RESTful APIs. OData is based on widely accepted web standards like HTTP, REST, and JSON, and it enables the creation of data APIs that can be easily consumed by a wide variety of client platforms, including web and mobile applications.
Describe the solution you'd like Some of the benefits of using OData include:
Interoperability: OData allows data to be shared and consumed across different platforms and devices. This makes it easier for developers to create applications that can work with different data sources.
Standardization: OData provides a standard way of creating and consuming RESTful APIs, which means that developers can rely on consistent behavior across different implementations.
Queryability: OData supports rich query capabilities, including filtering, sorting, and pagination, which makes it easier to retrieve and work with large amounts of data.
Security: OData supports various authentication and authorization mechanisms, which makes it easier to secure data and control access to it.
Tooling: OData has a rich ecosystem of tools and libraries that make it easier to create, test, and consume OData APIs.
Additional context I think one endpoint like getAll and getById can apply OData and back-office and both mobile can get what they really want.