KB-1771 "HTTP/1.1 415 Unsupported Media Type" error returned when testing an HTTP request using an Integration Object


When configuring an Integration Object where the content type of the HTTP request is specified in the body, testing the request returns an "HTTP/1.1 415 Unsupported Media Type" error as depicted below:


When the content type of the HTTP request is solely specified in the request body, by default, Appian appends charset=UTF-8 to the selected content type. While this is the intended behavior, certain systems will reject requests where the body is UTF-8 encoded.

A workaround for this issue was implemented via AN-107124 in Appian 18.1 Hotfix Package D.


  1. Ensure that the environment is running on Appian 18.1 (Hotifx Package D) or later by applying the latest hotfix to your Appian installation or upgrading to the latest version of Appian.
  2. Within the Integration Object configuration, override the default charset=UTF-8 encoding by adding a row to the HTTP header grid with the key "Content-Type". The image below illustrates an example of this for a HTTP integration with a content type of JSON:

Affected Versions

This article applies to Appian 18.1 and later.

Last Reviewed: November 2018