I'm seeing this same problem and it is extremely frustrating having my data held hostage and I can't access it. I call the API to retrieve the latest response(s) and there is significant lag. The responses seem to appear instantly in the Data & Analysis view of the survey administrator (/responses/#/surveys/) but that doesn't help me on the API side of things.



The problem seems to be even worse when I use the 'lastResponseId' parameter in the 'Create Response Export' call. After about 10 minutes the response might begin appearing IF I EXCLUDE the 'lastResponseId' parameter, but as soon as I add the parameter back in it stops returning the latest response.



Can this be fixed PLEASE!

---

Hey @Paola and @"w.patrick.gale"! Feel free to reach out to our Integrations team so they can take a closer look into this with you and escalate it if needed!

---

Thanks @LaurenK, I am waiting to hear back from the support team.

---

@Paola / @"w.patrick.gale",



Have you tried https://survey.qualtrics.com/WRAPI/ControlPanel/docs.php#getLegacyResponseData_2.5?

---

Thanks @TomG but why would we want to use a deprecated API? I do like that the older API allows for requesting responses from a single ResponseID. I will give it a try.

---

> @"w.patrick.gale" said:

> Thanks @TomG but why would we want to use a deprecated API?



Because it may work when the newest API doesn't.

---

I am fairly certain the issue I am seeing with latest responses not appearing in the zip file relates to v3.0 of the API and using parameters such as startDate. The parameters I am using in my case are:



$fields = array(

'surveyId' => $strSurveyId,

'format' => 'json',

'startDate' => '2018-09-18T00:00:00Z',

'useLocalTime' => true

);



I made a number of calls to v3.0 API to try and get a new response to appear in the returned zip file but it was not appearing, however I made a simple GET request for the response ID using v2.5 of the API and it returned the response data. Yet even after I was able to retrieve the response using v2.5 API I was still unable to get the response using v3.0 API until trying again an hour later.



I submitted the issue to Qualtrics Support.

---

Qualtrics support suggested I add an 'endDate' parameter to the API call to prevent latency (at least while they look into the cause of latency when endDate is not used). I modified the fields parameters to include an 'endDate' two days into the future and so far NO MORE LATENCY ISSUES. That seemed to do the trick for me. Two thumbs up.

_(Note this issue pertains to API v3.0 calls to https://yourdatacenterid.qualtrics.com/API/v3/responseexports)_



$fields = array(

'surveyId' => $strSurveyId,

'format' => 'json',

'startDate' => '2018-09-18T00:00:00Z',

'endDate' => '2018-09-20T00:00:00Z',

'useLocalTime' => true

);

---