TMview 's search endpoint takes a criteria field in every request:
{ "page" : "1" , "pageSize" : "50" , "criteria" : "C" , "basicSearch" : "solarwinds" }
Enter fullscreen mode
Exit fullscreen mode
The web UI always sends "C" , and so did our Actor when we started digging — it's the only value anyone writes about, because it's the only value the UI ever exercises. We tried the rest of the alphabet against the live endpoint to see what else the parameter accepts.
Only three values work, and lowercase doesn't count
Fourteen single-character and empty values, same query, same headers, one second apart:
criteria Result
C 200 , 148 matches
E 200 , 71 matches
W 200 , 147 matches
S , X , 1 , 2 , empty string 400
c , s , e (lowercase) 400
Every rejected value returns the same structured error, not a silent empty result:
{ "severity" : "INFO" , "code" : "PARAMETER_INCORRECT_FORMAT" , "type" : "VALIDATION" , "status" : 400 }
Enter fullscreen mode
Exit fullscreen mode
So the enum is exactly three…