Hi @EmilyG, do you have code that you can share? it's tough to diagnose the issue without seeing the api requests you're sending
You could make a dedicated API user that has access to all your surveys and then share its token with each other user.
The new version of the response export api (https://api.qualtrics.com/docs/create-response-export-new) respects edited responses. Overall, the process for getting responses is very similar, so if you're comfortable with the legacy api you should be fine here. One thing to note - the new api does not respect edited question names, while the legacy api does. I'm not sure if this was an intentional change, but it's something to look out for.
As TomG says, qsf files are written in json, but their content is slightly different from from the API export. For instance, qsf files include display, skip, and flow logic which is not present in the API export. Whether you can rely on the API depends on whether your application demands this additional content.
@TomG I would also be very interested in this code. Would you mind sharing it with me as well?
Occasionally, I've found that qualtRics will throw that error when nothing is wrong, and that repeating the command will result in success. In my experience, 404s happen because of a hitch in the two stage response export process that getSurvey() is managing. If you haven't already, try running it again. Try other R x Qualtrics API packages like qualtricsR, https://github.com/jamesdunham/qsurvey, then if those don't work try opening up a jupyter notebook and following the python tutorial in the API documentation.
Already have an account? Login
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.
