Interestingly enough though.

This suggests to me (although I may be mistaken) that Outsystems needs the Accept (in the client request) Content-Type(in the APIs response) to be exactly the same.
Option 1:
So now my question could be, is there a way to remove charset=utf-8 from the response. Does it even make sense that doing this would work ?
Option 2:
Would it be possible to edit the clients request to add an Accept header of charset=utf-8.
Question:
Is it possible that this is an encoding problem ? This link talk about encoding problems, but I am not sure if this is relevant here.
https://www.outsystems.com/forums/discussion/16634/rest-encoding-problem/
How I understand this situation is.
- Client request is saying "I Accept text/xml only"
- the api response is saying " I am giving you content type text/xml and it is utf-8 encoded"
- Outsystems error logic is going "I have compared the request and the response and determined that the conversation is not compatible - therefore there is a 406 error and which means it relates to the accept header"
Unfortunately up till now I assumed the accept header had to be talking about the text/xml, but the Accept also relates to the encoding. Do you agree ?