Character Notification endpoint needs to display humanized msg.

[c0dezer019]

Character Notification endpoint needs to display humanized msg.

[wfjsw]

You can always generate a readable description as you like by parsing the notification payload? Parsing it server-side would dramatically increase the load since it would query databases more and many consumers are polling that.

[cvweiss]

APIs are meant to be consumed by computers and then formatted for human presentation depending on the criteria.

I propose closing this issue.

[c0dezer019]

This would require rather complex localization from ESI side to support multiple languages. While the notification format is not great, it does its job and the abstraction using notification codes is just fine. User friendly strings don't fit well.

It would not. The app developer can translate it themselves on their end as there are plenty of i18n libraries out there.

[NathenSample]

As has been said the API endpoints are designed for machine consumption not human consumption - As a general rule of thumb CCP avoid "pre-cooking" their data, and instead expect you to make use of either other endpoints, or the SDE when building human readable strings.

I'll be closing this for now.

[evanova]

This would require rather complex localization from ESI side to support multiple languages. While the notification format is not great, it does its job and the abstraction using notification codes is just fine. User friendly strings don't fit well.