Integration Response data Garbled (UTF-8)

RE: Integration Response data Garbled (UTF-8)

Stefan Helzle — Wed, 02 Jul 2025 14:13:39 GMT

Try to call that API using a tool like Postman, and verify that the data is actually encoded in UTF-8. I have seen APIs claiming to use UTF-8, but using a different encoding in the end.

RE: Integration Response data Garbled (UTF-8)

Mathieu Drouin — Wed, 02 Jul 2025 12:28:09 GMT

I'd suggest trying in Postman, could just be an issue with Appian's UI.

RE: Integration Response data Garbled (UTF-8)

dreamyoung — Wed, 02 Jul 2025 10:34:31 GMT

Hi, this is how the integration is setted.

The headers are setted as Content-Type: application/json; charset=UTF-8

cannot find why the Korean is grabled.

RE: Integration Response data Garbled (UTF-8)

dreamyoung — Wed, 02 Jul 2025 10:34:25 GMT

Hi, this is how the integration is setted.

The headers are setted as Content-Type: application/json; charset=UTF-8

cannot find why the Korean is grabled.

RE: Integration Response data Garbled (UTF-8)

Stefan Helzle — Wed, 02 Jul 2025 08:39:27 GMT

[quote userid="55805" url="~/discussions/f/integrations/39385/integration-response-data-garbled-utf-8"]Korean text is not displaying correctly[/quote]

What exactly does this mean? What do you do with the data until it is displayed?

RE: Integration Response data Garbled (UTF-8)

Megha Ramnani — Wed, 02 Jul 2025 07:28:27 GMT

Hello,

Since both the API provider and Appian use UTF-8 encoding, the garbled Korean characters likely indicate an issue with how the response is being interpreted or displayed within Appian, check the below first:

The API response has Content-Type: application/json; charset=UTF-8.

The integration parses the response as JSON or text.

Try the same API in Postman to verify if the characters appear correctly outside Appian.

Sharing the response headers and sample output will help us debug further.