Quick Summary: The request was understood but violates a SkillsDB rule. The
detail states the rule; change what you are asking for, not just the syntax.What happened
Unlike a 400, everything about the request was syntactically valid — the combination is what gets rejected.Known rules
- Assessments require proficiency grading: enabling a career
assessmentssetting whileproficiencyGradingis disabled is rejected rather than silently accepted. - Career library management disabled: authoring careers over the API requires the same company module setting the app enforces.
- Reorders must be complete: reordering labels, certification types or a learning library reference list (learning types, training providers, formats, audiences or course levels) takes every id of that group exactly once, in the desired order. A partial, duplicated or unknown id list is rejected.
- Grades must belong to the career: recording career grades for a person rejects any skill that is not part of that career for that person.
- Person certifications must fit the person’s current state: a certification that cannot be recorded for the person as things stand is rejected.
- Learning library and survey writes the app would refuse: when the same operation in the app would fail, the API answers 422 and the
detailcarries the app’s own message.
What to do
Read thedetail, change the request to satisfy the rule (for example enable proficiency grading in the same PATCH), or ask an administrator about the relevant company setting.