When configuring an HTTP integration with a body, you must choose a value in the Content Type dropdown. In all cases, this dropdown will set the "Content-Type" header on your request. The sections below provide more information on the individual content types and what they mean in the context of the integration.
The Document and Multipart Form Data Content Types can be used to send binary documents with your integrations
a!toJson(). You should not use this content type when sending primitive types.
eXtensible Markup Language (XML) is a data-interchange format that is commonly used for SOAP web services, though it is also compatible with REST. It is composed of nested units called elements that form data structures similar to Appian dictionaries and complex data types. When selecting this value for your Content Type, you need to manually convert Appian data to XML. To convert an Appian value to XML, use
toxml(). In general, you should not use this content type when sending primitive types.
The Document Content Type option allows you to send files to external systems. Choosing this option affects your request in three ways:
In HTTP, multipart requests are used to send multiple types of data in a single request – generally structured text and unstructured binary data. This often boils down to sending JSON or XML data alongside files. In Appian, choosing the Multipart Form Data Content Type option allows you to configure such a request. The list below provides details on configuring multipart requests in Appian. For more information on multipart requests in general, see the RFC.
Choosing this option sets the Content-Type header
text/plain, which is the generic media type for plain text. This content type is rarely used by APIs.
Selecting the Custom option allows you to set content-type manually. This should be used when you cannot leverage any of the provided content-type options. Note that only text-based media types can be sent through integrations in this way, and the charset will automatically be set to UTF-8.