Lots of meaningful characters are permitted in XIDs! Some functions rely on XIDs not having those characters - for instance the GET /v1/point-values/{xids}/multiple-points-single-array uses comma separation for the XIDs. I noticed I downloaded data from the wrong point (DP_1,000 downloaded data for DP_1)!
I imagine there are a few other characters to break things with. % seems like it breaks some of the old pages (get point by XID on old data point details). It also seems to mess with the RQL
Perhaps we should validate? Perhaps these are undocumented features for how to deny using certain endpoints?
Lots of meaningful characters are permitted in XIDs! Some functions rely on XIDs not having those characters - for instance the GET /v1/point-values/{xids}/multiple-points-single-array uses comma separation for the XIDs. I noticed I downloaded data from the wrong point (DP_1,000 downloaded data for DP_1)!
I imagine there are a few other characters to break things with. % seems like it breaks some of the old pages (get point by XID on old data point details). It also seems to mess with the RQL
Perhaps we should validate? Perhaps these are undocumented features for how to deny using certain endpoints?