/api/v1/users/:user_id/files/quota UNAUTHORIZED

[erlend_thune]

I am trying to use

/api/v1/users/:user_id/files/quota

documented here Canvas LMS REST API Documentation​

F.ex. https://ikt.instructure.com/api/v1/users/312/files/quota

Even when I am logged in as an administrator, I get "while(1);{"status":"unauthorized","errors":[{"message":"user not authorized to perform that action"}]}"

My plan was to get an overview of the quota used by all the students to see if we should increase it.

[garth · Accepted solution]

 @erlend_thune ​ it seems you have two options here:

• Implement OAuth2 and request a token on the users behalf
  • OAuth2​
• Impersonate the user
  • Masquerading

If this is an interal report, Masquerading would likely be the easiest approach.

Your syntax for the call would look like this:  

/api/v1/users/:user_id/files/quota?as_user_id=:user_id

Let me know if this helps.

[erlend_thune]

Thanks a lot! I only need it to check if any of the students are getting close to their file quota, so the

/api/v1/users/:user_id/files/quota?as_user_id=:user_id

worked perfectly!

[garth]

Awesome, thanks for the feedback.

[buellj]

 @garth ,  @erlend_thune  I'm getting the same error despite adding the masquerade string. Example URL: https://seattleu.instructure.com/api/v1/users/12345/files/quota?as_user_id=45678 

12345 is the user I'm trying to see the file quota for and my own user ID is at the end. 

[erlend_thune]

You must use the same user id both places, i.e.  https://seattleu.instructure.com/api/v1/users/12345/files/quota?as_user_id=12345

I guess the as_user_id masquerades you as that user before it runs the command. 

[buellj]

That did it! Thanks  @erlend_thune ‌! It seems a bit counter intuitive to require masquerading for that call to work and Instructure should add that info to their documentation. 

[garth]

 @buellj ‌ I apologize for the incorrect example that I posted, not sure what I was thinking, sorry for the trouble it may have caused.

[buellj]

Absolutely no worries  @garth ‌ - I wouldn't have found the solution without your response so a huge thank you!!! We just created a first version of a Node JS app that reads a CSV (the user provisioning report), does a bunch of API calls to get the quota used and then stores that in another CSV file. 

[erlend_thune]

Yes,  @garth ‌. If someone is to blame, it is me. I should have posted a message about it the moment I found out! Your response saved me to!