Celebrate Excellence in Education: Nominate Outstanding Educators by April 15!
Found this content helpful? Log in or sign up to leave a like!
We're doing some testing in beta related to pushing grades into an assignment. We'll publish the assignment and then make it available. Then we make a PUT query something like below.
/api/v1/courses/1677/assignments/78614/submissions/13627?submission[posted_grade]=21&access_token=XXXX
The token related to this call has full access to our instance.
However, we often get the JSON response below
{"status":"unauthorized","errors":[{"message":"user not authorized to perform that action"}]}
This will sometimes fix itself overnight and allow us to put the grades in without changing anything about the query.
Has anyone encountered this? Is there a reason time alone would move this from a "not authorized" query to one that works perfectly?
Ok, I know this is an old post and nobody responded but I'm curious if you were able to fix this.
If I had to guess the reason why this didn't work for some of the students is that they haven't logged into Canvas their first time yet and clicked the Authorize prompt they get the first time.
We're trying to work around this now with a pass for students from our student portal into Canvas.
If I'm correct and you were able to come up with a way to do this please let me know.
To participate in the Instructure Community, you need to sign up or log in:
Sign In