Hi @david_amore
I noticed as per the documentation, the hide_points setting is only described in the structure of the RubricAssociation object. However, neither the create nor update RubricAssociation endpoints seemed to support this parameter. It's read-only and I've confirmed based on my testing. Hence, I had to go the chrome inspect route.
My approach was to create a global Rubric at the account level and do a RubricAssociation with each assignment using the API. The assignment will have the rubric attached but points will not be removed (as it's not supported on the API). However, using the payload that you retrieve via Chrome Inspect and via the POST request that you do to perform the RubricAssociation, you get a few dynamic results from this response. You can use these to "update" your RubricAssociation once again using a PUT request.
I've listed the bits for the payload that you will need. The rest will depend on the content in your Rubric.
'rubric_association[id]': page_response["rubric_association"]["id"],
'rubric_association_id': page_response["rubric_association"]["id"],
'rubric_association[association_id]': page_response["rubric_association"]["association_id"],
'rubric_association[context_id]': course.id,
'rubric_association[context_type]': 'Course',
'rubric_association[association_type]': 'Assignment',
'rubric_association[use_for_grading]': '0',
'rubric_association[purpose]': 'grading',
'rubric_association[hide_score_total]': '0',
'rubric_association[hide_points]': '1',
'rubric_association[hide_outcome_results]': '0',
'rubric_association[context_code]': "course_" + str(course.id),
'rubric_id': rubric_id,
'skip_updating_points_possible': False,
I had some existing code and had to get things done quickly You can probably do this better and maybe skip a step.
Cheers,
Raj