I propose to undelete the deleted parts and search for time/funding/ways to improve this. Either here (wikipage) or at another well-defined place: RPC-API autodoc?

Dennis, just deleting the information was a bad decision. Can you transfer the missing documentation to the source code, please?

Maybe I can help here: I have some ideas about the readability of the doc pages. For example (nearly) all headings at:
https://api.limesurvey.org/classes/remotecontrol_handle.html
start with " RPC Routine to ..." making this page hard to read.

Proposal for change:
" RPC Routine to return settings of a token/participant of a survey "
change to:
" Participant: get settings (token table)"

and

"RPC routine to to initialise the survey's collection of tokens where new participant tokens may be later added."
change to:
"Participant: initialize use of participants (token) table"

At least some format, where the main object that you work on is mentioned first.

I am prepared to work on this. If you tell me where I have to watch out for I will make a pull request for it.

Maybe the available properties can be mentioned here to.

PS : in don't find the original issue : but i'm sure we have a discussion about this removing.

See https://github.com/LimeSurvey/LimeSurvey/pull/704

@tammo : i think some settings must be needed, and some other : we can leave it for starting. Did you have a list where the actual information didn't allow a dev to use it ?

PS : about get_survey_properties: it's included in \Survey model then we can only show a @see \Survey because if we update \Survey : we surely didn't update remote_control file .....

See : https://github.com/LimeSurvey/LimeSurvey/pull/704/commits/c3f1a233b04703cd357188d5b15ee1503f773e7e

you don't know property name ? Get them whole. It's the best solution for dev here ....

@tammo and @c_schmitz : see https://limesurvey.sondages.pro/admin/remotecontrol with collapse. Seems better no ?

I think that what Dennis shows in the link to https://limesurvey.sondages.pro/admin/remotecontrol is a great advancement.

This would be a great starting point for further development, perhaps with also showing some examples. There are still some speling mistakes, but that can easily be corrected.

@DenisChenu: you stated: "you don't know property name ? Get them whole. It's the best solution for dev here .... "

I am not really sure what you mean here.

@DenisChenu: you don't know property name ? Get them whole. It's the best solution for dev here ....

If you meant to say: "get them all", I agree fully. I think that when you do not know specifics, it would be great to ask for "all", maybe even by default.

Like in token attributes, survey properties, languages atc.

Get them all : before
@param array $aSurveySettingsThe properties to get
now
@param array|null $aSurveySettings (optionnal) The properties to get
If null : return all

I make same for get_participant_properties, get_question_properties, get_group_properties and get_language_properties. Please see updated https://limesurvey.sondages.pro/admin/remotecontrol documentation with https://github.com/LimeSurvey/LimeSurvey/pull/704

hero!

@tammo, thanks. i make some test this morning if it's OK and merge it.

Fix committed to master branch: http://bugs.limesurvey.org/plugin.php?page=Source/view&id=22881

@tammo : if you can fix speling mistakes please. About improvments , i think we can

1. Control if MarkDown is OK in https://api.limesurvey.org/classes/remotecontrol_handle.html#method_get_survey_properties
2. If yes : use it more and more
3. Maybe trying @link for \Survey : see https://api.limesurvey.org/classes/Survey.html#property_format , i think we can/must add @var in each properties to have a clean view of attributes.

PS : see https://api.limesurvey.org/errors.html#application/models/Survey.php for example

Version 2.65.4 (build 170612) released.