This is definitely defect territory, not an API limitation. The bug occurs whenever an accented character is submitted to the API. API documentation shows many example requests and responses in UTF-8 format, but the API does not actually respect requesting a different format. It appears to only use CP-1252 which, when sent UTF-8, will result in the issues explained here: http://string-functions.com/encodingtable.aspx?encoding=65001&decoding=1252
This is definitely defect territory, not an API limitation. The bug occurs whenever an accented character is submitted to the API. API documentation shows many example requests and responses in UTF-8 format, but the API does not actually respect requesting a different format. It appears to only use CP-1252 which, when sent UTF-8, will result in the issues explained here: http://string-functions.com/encodingtable.aspx?encoding=65001&decoding=1252
This is essential.