Webservice endpoints plurality?

[pjdevries]

Is there a specific reason why endpoint v1/content/article, to request a list of articles, is singular and v1/content/categories, to request a list of categories, is plural? Even more confusing, v1/fields/content/articles is also plural.

[pjdevries]

To be more clear and avoid confusion: I am not debating whether it should be singular or plural. I am just wondering why we have this inconsistency.

[Fedik]

I do not know the reason,
but I suspect it is coincidence

[alikon]

so v1/content/article should be v1/content/articles for consistency right ?

also
v1/content/article/contenthistory/ should be v1/content/articles/contenthistory/
v1/content/article/contenthistory/keep should be v1/content/articles/contenthistory/keep

[alikon]

please test #34093

[joomdonation]

+1 for using plural.

[wilsonge]

The original spec we did in 2017 GSOC was singular (ref: https://joomla-projects.github.io/gsoc19_webservices/?specification/chapters/urls-and-routing.md).

Generally speaking though as long as it's consistent I don't mind hugely. It's worth noting though that the type of the object returned in the JSON API payload MUST be singular - so if we want to do plural URLs it's worth noting that the type in the body of the resource will always still be the singular version.

[joomdonation]

For some systems I have worked on like Mailchimp, Bubspot... (integration with their REST API only for my extensions) , they always use plural (even WordPress use plural, too). So maybe it is a standard or best practice :).