REST APIs are set up by default to handle JSON data, but can also handle other data formats.
When a message arrives on the Input node of a subflow for an implemented operation, the message domain of that message is set to JSON. You can handle other types of data in a subflow for an implemented operation by using a ResetContentDescriptor node to change the message domain of the message before any message parsing is performed.
You can also use a Route node to handle multiple types of data in the same subflow. You can configure the Route node to route data to a ResetContentDescriptor node based on the Content-Type header in the request message. The Content-Type header can be added to the request by the HTTP client, and is used to describe the type of the data in the request.
To handle non-JSON data in a REST API, complete the following steps: