I agree @anibalsanchez - when writing the JCM article it was a saga to find enough information, as well as know correct terminology to use (vs what had been implemented so far).

I propose a checklist to move forward with making the changes. Open to additions.

Confirm terminology

• ✅ Use "Joomla! 4.x Web Services" for specific references to Joomla Web Services
• ✅ Use "Web Services" as the general reference to Joomla Web Services

Joomla Docs

• ✅ Create new JDOCS Category: "Joomla! 4.x Web Services" - https://docs.joomla.org/Category:Joomla!_4.x_Web_Services
• ✅ Add "Joomla! 4.x Web Services" and "Joomla! 4.x" to existing articles related to Web Services
• Update https://docs.joomla.org/Joomla_Api_Specification to swap API to Web Services
• Update https://docs.joomla.org/J4.x:Adding_an_API_to_a_Joomla_Component to swap API to Web Services
• Update https://docs.joomla.org/J4.x:Joomla_Core_APIs to swap API to Web Services
• Configure JDOCS redirects for old URLs for all of these articles.
• ✅ Configure redirect for old category to new category
• ✅ Revisit https://docs.joomla.org/Web_Services_Working_Group and reset category - added to new category.

PR Required
Adjust plugins to updated terminology:

• ✅ Web Services - Banners
• ✅ API Authentication - Basic Auth
• ✅ API Authentication - Joomla Token

Magazine Article

• @particthistle to edit article and update to new terminology https://magazine.joomla.org/all-issues/august-2020/joomla-web-services-api-101-tokens,-testing-and-a-taste-test

Joomla Docs Longer Term

• Add individual detail pages for each Web Service listed in https://docs.joomla.org/J4.x:Joomla_Core_APIs
• On individual detail pages, add example usage cases and complete mapping of field syntax that can be used for each Web Service request.

Joomla 4.1 Enhancements

• Improvements to Web Services Authentication to allow use by other ACL levels (currently only Super Users)
• Review Roadmap - is everything there?
• Are there other features that can be considered to include in Web Services for Joomla 4.1?

Official 3rd Party Integrations

• Zapier
• IFTTT
• Integromat

Tags to add: Documentation Required, RFC

Thinking in terms of the plugin names, it would be clearer:

• Web Services - Banners
• Web Services Authentication - Basic Auth
• Web Services Authentication - Joomla Token

We need to avoid the use of API. The regular Joomla user doesn't know what is an API. On top of this, API can refer to any API of the system. In all of these cases, we are talking only about "Web Services".

One more point, in the WordPress ecosystem, a similar feature to Joomla "Web Services" is named "REST API". API is qualified with "REST"; so the API is always going to be "RESTful Web services".

So, changing to "Web Services" on Joomla helps to differentiate the feature and define a wider scope for future development.

Admin: Not sure why the label:RFC got dropped by the bot. @anibalsanchez do you want to add [RFC] to the subject line?

I've added ✅ to the items I've updated so far.

There's a few of the JDOCs that are going to need more of a coder's eye, as there's some function names and framework references that need refactoring to change what the impact may be of /api/ folder as an example.

I have just done the label and title stuff ?

@particthistle My report is about the displayed name in the user interface and in the documentation. It must be "Web Services".

There's no need for refactoring or complicating the issue. If coding people are happy calling Web Services as API internally, there is no issue with that.

Is it only me, but Web Services is the wrong name. It is a Rest API. Not mor or less, or not? Web Services is too general...

"Web Services" is a more general concept than "Rest API"; it includes the "Rest API" as a special case. So, "Web Services" is not wrong. @laoneo

In the future, Joomla Web Services could also support SOAP APIs or GraphQL APIs.

@wilsonge a decision needs to be made on this before RC so we have time to update strings and docs if required

I'd prefer webservices I think as the term inside the CMS. We're not limited to just REST (even if that's what we are providing out the box). However the directory in the CMS should remain as API as by convention most websites use the /api/ path in their API urls

Based on this (https://en.wikipedia.org/wiki/Web_service) can we agree to go with "Web services"

Based on the comments of Anibal, George and Brian, I would support "Web Services" too.

as #32496 has been merged shouldnt this be closed now or is there something outstanding?

My checklist is a wider note on what else needs to be changed in regards to making Web Services something people uptake.

The issue @anibalsanchez has raised may be much simpler in regards to Joomla 4 changes, and may be able to see this issue closed.

The only suggestions remaining from @anibalsanchez's list are whether to rename these plugins:

• API Authentication - Basic Auth
• API Authentication - Joomla Token

Should these become:

• Web Services Authentication - Basic Auth
• Web Services Authentication - Joomla Token

@particthistle You are right in the sense that naming the plugins as Web Services Authentication would be much clearer. However, the plugin group has already be named as api-authentication. So, following the Joomla naming conventions for plugins the plugin group prefix must be API Authentication.

I think it would be better to name the plugins as:

• API Authentication - Web Services Basic Auth
• API Authentication - Web Services Joomla Token Auth