From ec3e0edca1ecae369f077f61318225bb444e04ad Mon Sep 17 00:00:00 2001 From: HermanPeeren Date: Wed, 18 Nov 2026 21:50:19 +0100 Subject: [PATCH] Release 6.2.2: response attributes that the API views render info.version is 6.2.2; CHANGELOG.md has the 6.2.2 section with the changes of joomla-projects/API-Endpoints#6. --- CHANGELOG.md | 4 +++- src/joomla-ws-api.json | 2 +- 2 files changed, 4 insertions(+), 2 deletions(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index 52219c2..fe2d414 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -3,7 +3,7 @@ Each release describes the core Web Services API of one Joomla minor version: release 6.2.x is for Joomla 6.2. A patch release (6.2.1, 6.2.2, ...) improves the description of the same API. -## Unreleased +## 6.2.2 Response attributes now match what the API views of Joomla render (checked against joomla-cms 6.2.0 and `6.3-dev`, whose API code is the same): @@ -15,6 +15,8 @@ Response attributes now match what the API views of Joomla render (checked again - `urls` removed from the attributes of the article list: the list query does not select it. - `articletext`: the request bodies of articles say that it has no effect on update, and that `introtext` and `fulltext` win over it on create. +- The `tags` of contacts and newsfeeds describe a bug in Joomla: with more than one tag, a title can be paired + with the wrong tag ID (the same bug was fixed for articles in Joomla 4.4.0). ## 6.2.1 diff --git a/src/joomla-ws-api.json b/src/joomla-ws-api.json index 5fad7fa..d89d53a 100644 --- a/src/joomla-ws-api.json +++ b/src/joomla-ws-api.json @@ -2,7 +2,7 @@ "openapi": "3.1.0", "info": { "title": "Joomla 6.2 Core Web Services API", - "version": "6.2.1", + "version": "6.2.2", "description": "Core Joomla Web Services API routes, authentication, request and response schemas, and form parameters. Check x-support for operation availability. Replace example URLs, tokens and IDs with site values. Installed plugins can extend forms and responses.\n\n## Authentication\n\nAuthentication is done using a Joomla API Token, sent as `Authorization: Bearer ` or in the `X-Joomla-Token` header. To get the token, go to the user profile in your Joomla installation and activate and copy the API key. Basic authentication with username and password only works when its plugin is enabled. The Joomla Update endpoints use the separate `X-JUpdate-Token`.\n\n## Response schemas\n\nResponse schemas and examples are derived from the Joomla source code; they are not captured from a site, unless the example says so.\n\n## Components without web services\n\n* com_associations supplies administrator tools for multilingual associations. It has no standalone web-services plugin or REST routes in these snapshots.\n* com_finder manages the Smart Search index, maps and filters. It has no core REST search or indexing routes in these snapshots.\n\n## Videos\n\n[YouTube playlist about Joomla Web Services / APIs](https://www.youtube.com/playlist?list=PLsg93PS_2NeL850YZFlAi1Eb7hwxETNkX)", "license": { "name": "GPL-2.0-or-later",