To override the Content-type in your clients, use the HTTP Accept Header, append the .xml suffix or ?format=xml
HTTP + XML
The following are sample HTTP requests and responses.
The placeholders shown need to be replaced with actual values.
POST /stripe-checkout-session-2 HTTP/1.1
Host: duengageapi.uat.scadsoftware.com
Accept: application/xml
Content-Type: application/xml
Content-Length: length
<StripeRequestCheckoutSession2 xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/digitaluapi.ServiceModel">
<CampaignActionsRequestsId>0</CampaignActionsRequestsId>
<CancelUrl>String</CancelUrl>
<CommsGuid>00000000-0000-0000-0000-000000000000</CommsGuid>
<Description>String</Description>
<Email>String</Email>
<SuccessUrl>String</SuccessUrl>
</StripeRequestCheckoutSession2>
HTTP/1.1 200 OK
Content-Type: application/xml
Content-Length: length
<StripeCheckoutSessionResponse xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/digitaluapi.ServiceModel">
<Url>String</Url>
</StripeCheckoutSessionResponse>