I'm pushing data to a Streaming Data API endpoint using JSON. In this case, it's just a single channel and a date.... { "Temperature": 12.42, "Date": <date stamp in the correct format> ...
At the end of the day it should simply be consistent - either refuse to accept JSON channels that have a different case (which would be very bad in my opinion, but at least it would be consistent), or remove the case-sensitivity from Subscribe (the preferred choice) to allow streaming data to work when there are case differences between the JSON and the configured channels.