Access denied trying to access export

  • 14 February 2023
  • 3 replies

Hi all, I’m having some trouble debugging an issue with downloading an export.  I’m able to create it, and in one of my clients (custom curl implementation) I’m also able to download it, but not in another and so I’m trying to diagnose why that is.


However, even when I try to follow the steps here:, I’m getting “<?xml version='1.0' encoding='UTF-8'?><Error><Code>AccessDenied</Code><Message>Access denied.</Message><Details>Anonymous caller does not have storage.objects.get access to the Google Cloud Storage object. Permission 'storage.objects.get' denied on resource (or it may not exist).</Details></Error>” back from the Google Storage APIs.  


I’m copy and pasting the ‘location’ field coming back from{id} directly into another curl call and that’s what’s failing.  


Any suggestions?  I suspect there’s an encoding issue with the storage location’s URL but I can’t seem to get to the bottom of it.  




Best answer by lindsay 14 February 2023, 15:52

View original

3 replies

Userlevel 4

Hey@Perry! Thanks so much for chatting in! 😊

After taking a look at the error message you’re experiencing here, it looks like the issue may be related to  & symbols in the location response. This is something we've seen before, and we've added a note in step 4 (Download the file) to address this scenario. In this case, you'll want to use the echo command within the curl command, like this:

curl -JO $(echo "<location>")

Alternatively, you can manually change that encoding to be able to access the file location URL.

I hope this helps! If this does not resolve the issue, could you please provide the full URL for the 'location' Response?

Thanks so much! 🤞


Thanks, yes I found those other instructions (would be good for them to be in the main API docs as well).  I was able to get it working via my own manual curl, but I’m still hitting some odd encoding issues going through my custom application.  That’s on me to fix now that I have a working example, so thank you!

Userlevel 4

Hey @Perry! Thank you for the followup!

I have sent a request to our team to update the main API docs with this information as well- thanks for catching that! 

I’m glad you were able to get it working on your own manual curl. Please let us know if we can be of any support moving forward. 😊