These values are part of a configuration format, meaning they are already part of an external API. Being able to change the name of these keys seems like a weak argument considering that changing the name of these keys is a breaking change that should only be done in the most extreme cases.

This approach of defining constants for configuration keys could also lead to inconsistencies in the SDK. For example, would we add constants for configuration formats that have nested hashes and keys?