Running a campaign not able to validate vanilla ckan api base url

[Deleted user]

When running a campaign, there is a text input box to enter the base api url.
An example is given:
http://data.mysite.uk/api
I notice that when hitting this url you indeed get a json response of {version: .. }

However I'm not sure that this behaviour exists in any of the recent vanilla ckan api docs or code.
An example of a prod website that resembles what I believe is this default api is at:
https://data.qld.gov.au/api
This returns a 404.
My own running of local and uat ckan instances also replicates this behaviour.

Code update is needed to perhaps glean this version from another means - I would suggest using the util/status call which will return a {...., ckan_version: .... }.
This could be done on receiving a 404 from a url which has passed preliminary validation.
That way if this status api call was successful and the 'ckan_version' attribute was present, the validation could still pass.