This is the “magic number” that starts a PNG file, except the first byte with a value of 0x89 has instead been replaced with the Unicode replacement character (\uFFFD).
The data was already corrupted by the time it got to whatever printed that log line; you’ll need to look earlier in the call stack for where things are going wrong.
It will help troubleshoot if you can capture exactly the bytes that the API is replying with - my suspicion is that it’s sending something like:
"html":"<BYTE 0x89>PNG<BYTE 0x0D><BYTE 0x0A>...etc...
which is problematic from both a “valid UTF8” and a “valid JSON” perspective.
