It is used to convert XML data coming from or returning to the client into a different format.

If this policy is used in the request line (Client → API Proxy → API), the message body from the client is transformed and transmitted to the Backend API.

If it is used in the response line (API → API Proxy → Client), the result is transmitted to the client by applying transformation on the message body returned from the Backend API.

The use of this policy makes sense if the message body from the client is XML.


Apinizer supports XSLT 1.0 and XSLT 2.0 for XML transformation operations.

The picture below shows the policy settings:


The policy fields are shown in the table below.

Field

Description

Name

The name can be written to facilitate the use and management of the policy. You will need this name during the management and selection of policies.

Description

An optional description of the policy that may be useful for usage and management activities.

Message Type

The message type can be selected as XML to XML or XML to JSON.

XSLT Value

XSLT script required for conversion is entered. (You can visit the XSLT Examples page for XSLT examples.)


For detailed information on how to test XSLT scripts written for message transformation, you can visit the XML Transformer page.

You can visit the Policies page for the details of the Conditions and Error Message Customization panels.