So we use the remote control API to download survey responses and transform them into a map (amongst other things).

The problem we have is that this process can't tell when it needs to run. We have to poll the survey server, and even then can't tell if the server has response data which need processing. So we process the whole lot every time.

This is not ideal. I've been looking for something in the API, or even the web UI, which can short-cut this process, and give us a list of response IDs which should be re-processed because they are either new, or modified. So far without success.

Can anyone suggest a way to do this?

Thanks!

In api.limesurvey.org/classes/remotecontrol...hod_export_responses

you have a variable : $iFromResponseID ,

Then if you already get until 1000 for id, you can set this var to 1000 the next time.
Need to keep current value in your tool.

Need to keep current value in your tool.

Or, use the API to record that in another "control" survey.

Thanks for the suggestion.

However, the responses sometimes get modified after their initial creation by an administrator or (possibly) the original user. I don't think this method would spot those changes would it?

Use afterSurveyComplete event : www.limesurvey.org/manual/AfterSurveyComplete

to send the id to your tool.

Can the `afterSurveyComplete` event fire many times, once after each modification?

I would also guess this would need us to write a plug-in, is that correct?

afterSurveyComplete : see the manual : when surey is submitted. Not when updated

An alterantive solution can be create you own API function.

See gitlab.com/SondagesPro/RemoteControl/ext...xportReponseFiltered for a sample.

Thank you very much for your help.

We're not self-hosting our LimeSurvey instance (we're on limequery.com), so we don't have access to the source code, and nor can we install 3rd party plug-ins:

www.limesurvey.org/manual/Plugin_manager...ird-party_plugins.3F

Sadly none of the suggestions so far seem to be both possible (for us) and cover the cases we need, i.e. to indicate when responses are modified.

Maybe you can contact limequery : account.limesurvey.org/customer-support

Why not use the end url to trigger your software to know that there have been changes?

Interesting idea but I don't think it covers the scenario where an admin updates the response in the back end.

Interesting idea but I don't think it covers the scenario where an admin updates the response in the back end.

Agreed, one would definitely need to reach the end of the survey to use this feature.