Sorry, but this is inconsistent, even if the doc says that's the way it is.
Then it's not. My design decision.
And to have it called "desc" just because that neatly has the same length as "path" is just irrational
Not really. And there is also a length limit for query strings, so keeping parameter names short leaves more room for
payload.
But that's in line with the incomprehensible fact that things are named in all lowercase on one side and in camelCase on another side,
Also a design decision I've made two years ago. Using all lower-case parameters makes the API language agnostic and works best across all platforms and programming languages.
The returned JSON of course follows the camelCase notation that is standard for JSON, especially in web environments.
When IMWS would return XML data, it would use dashes instead of camelCase. Because that's also standard.
It's really not that hard. Just remember once that parameters are always lower case, and the returned JSON responses are standard.
I'm already implementing IMWS 2, which uses slightly different and 'current' (aka 2019) naming conventions. But that version will not be used in the IMatch desktop context so you'll probably never have to 'face' it.