16 June 2026

Update to the updated_at attribute on GET partnerships when participant counts change in partnerships

We’ve updated how the updated_at timestamp behaves for GET partnerships to better reflect changes in participant activity.

What’s changed

The updated_at value on partnerships will now be updated whenever the number of participants currently training (ongoing participants) changes.

Previously, changes to this participant count were not reflected in updated_at, as the value is derived dynamically rather than stored on a specific attribute.

Why we’ve made this change

The number of participants currently training is an important part of the partnerships response. Not updating updated_at when this value changed meant lead providers could miss meaningful updates unless they re-polled all data.

This change ensures that updates to participant counts are returned consistently, making it easier for providers to detect and respond to changes.

What you need to do

No action is needed. However, lead providers should:

note that updated_at will be updated nightly when reflecting changes in the number of participants currently training
expect updated_at to change more frequently where participant activity changes
ensure your systems pick up these updates if you rely on updated_at for incremental data syncing
ensure your systems ignore any changes that you do not need to respond to. For example, if you only want to respond when the count changes from 0 to 1 or more