We should always use the nouns that represent the entity that we’re retrieving or manipulating as the pathname and always in favor of using plural designations.
It is always a good idea to use HTTP status codes according to its definitions to indicate the success or failure of a request.
In addition to the usage of HTTP status codes that indicate the outcome of the request always use a standardized responses for similar endpoints.
Collections usually grow overtime thus it is important to always return a limited and controlled amount of elements.
When a system grows, record properties grow as well in that process but not all of those properties are always required for clients to operate.
The Single Responsibility Principle focuses on the concept of keeping a function, method, or class, focused on a narrow behavior that it does well.
Consumers of your API should be able to understand how to use and what to expect from the available endpoints.