As title says, the /shortName endpoint does not reply with a valid JSON-encoded string but instead just returns a plaintext answer even though the response headers say that the response should be valid JSON:

Full paste of curl/jq test: http://xor.meo.ws/HLIIhwhWVTy4rZjS69YG_zQ13MQZNq2d.txt

fusl@linux-0lcz:~> curl -is "https://vrchat.com/api/1/instances/wrld_424c75c2-533c-4922-be0d-cd13c6aa6d6f:12345/shortName?apiKey=JlE5Jldo5Jibnk5O5hTx6XVqsJu4WJ26"

[...]

content-type: application/json; charset=utf-8

[...]

jeopardydaario-c35

fusl@linux-0lcz:~> curl -s "https://vrchat.com/api/1/instances/wrld_424c75c2-533c-4922-be0d-cd13c6aa6d6f:12345/shortName?apiKey=JlE5Jldo5Jibnk5O5hTx6XVqsJu4WJ26" | jq -r .

parse error: Invalid numeric literal at EOF at line 1, column 18