Rest API Explorer is escaping the special characters like single quote in the xml payload content.Issue <!-- div.margin { padding: 10px 40px 40px 30px; } table.tocTable { border: 1px solid; border-color: #e0e0e0; background-color: #fff; } .title { color: #d1232b; font-weight: normal; font-size: 28px; } h1 { color: #d1232b; font-weight: normal; font-size: 21px; margin-bottom: 5px; border-bottom-width: 2px; border-bottom-style: solid; border-bottom-color: #cccccc; } h2 { color: #646464; font-weight: bold; font-size: 18px; } h3 { color: #000000; font-weight: bold; font-size: 16px; } h4 { color: #666666; font-weight: bold; font-size: 15px; } h5 { color: #000000; font-weight: bold; font-size: 13px; } h6 { color: #000000; font-weight: bold; font-size:14px; } ul, ol { margin-left: 0; list-style-position: outside; } --> Overview Rest API Explorer is escaping the special characters like single quote in the xml payload content leading to insertion of incorrect data into the tables Subject We use Rest API Explorer from the platform to insert the data into tables using REST calls. The issue is that when we introduce special characters like 'apostrophe' in any of the fields on the input payload, they are escaped in the payload and incorrect or irrelevant data is inserted into the target tables when the REST call is executed from REST Explorer. Example In Rest API Explorer, try to send a rest request with below data. Make sure request format is application/xml. Observed that data is escaped. Data:table = incidentshort_description = rama'krishna output = rama\'krishna So the value of short description on the target incident record is inserted as rama\'krishna which is incorrect. Another example in the below screenshot: Work Around This issue is identified as a bug in REST API Explorer and is targeted to fix in New York release. Problem ticket is PRB1333220. The workaround is to use the response builder in REST API Explorer , then copy/paste whatever you want into the "Raw" builder and remove the extra escape backslashes.