NotificationID is reaching int32 limits
Hi all,
Just a quick heads-up: tomorrow or so we will reach the first NotificationID that doesn’t fit in an int32.
This mostly is relevant if you use /characters/{character_id}/notifications/.
The specs already state to expect an int64, and it has stated that for many years now. This post is mostly as a heads-up: please be mindful this number will no longer fit in an int32 soon.
Related, another route /characters/{character_id}/notifications/contacts/ is impacted. This route is almost never used by anyone (and I am serious here ... we had a hard time finding anyone actually using it). This route had the NotificationID set as an int32. This is of course wrong, and should be int64. A fix for this went out today. So if you are the only user of this endpoint, please be mindful of this change.
Anyway, that was all.
Cheers,
CCP Pinky