An error in the API for subparts was recently brought to our attention. We will be deploying an update to the API over the weekend of June 24 / 25 but wanted to make you aware of the change. While we don’t believe anyone will be affected by this change, it is possible that some users quietly used the incorrect API data.
Before the change, the subpart tags in a part’s part listing used part_revision_id to incorrectly reference the PARENT’S part revision ID. You’ll note that this was already referenced in the revision tag.
The API update changes this so that the part_revision_id now correctly references the CHILD part revision.