And while I’m here talking about changes, we’ve got one that’s going up on Monday: we’re dropping the level field from the assignments payload. That could be a biggy for some folks, so make sure your code still works without that field. The level filter on the assignments endpoint will still work, though.
If you’re wondering why, it has to do with our general move towards more independent and resilient objects in API v2.
Assignments have a subject, which belongs to a level. We want to make that relationship only exist once and make it clear when that relationship changes. By having the level field in the assignments, we have to either maintain that data in the millions of assignments out there (boy, does that suck to update when a subject moves around) and/or cache bust all the assignments delivered through the API when a related record changes.
Dropping it means we update a subject’s level, mark it as updated, bust the cache on that one record, and call it good. For y’all (and us internally), it does mean checking on those subjects periodically, but that has to happen anyway when a subject level changes.
TL:DR; we’re breaking things on Monday.