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.
GET /signup/api/nat/{nationalId}/group/{groupId}/templateType/{workflowTemplateTypeId}/key/{workflowCategoryKey}/type/{workflowTypeId}/revenue/{revenue}/subscription/{subscriptionInvoiceId}/years/{yearsOfService}/term/{termTypeId} HTTP/1.1
Host: devapi.billhighway.com
Accept: application/xml
HTTP/1.1 200 OK
Content-Type: application/xml
Content-Length: length
<FormBuilderMembershipPipelineRs xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/BH.CloudAPI.Common4.DTO.FormBuilder.Response">
<clientErrors>String</clientErrors>
<components xmlns:d2p1="http://schemas.datacontract.org/2004/07/BH.API.DataAccess.Pipeline">
<d2p1:BhWorkflowComponentDto>
<d2p1:ComponentName>String</d2p1:ComponentName>
<d2p1:HasClientError>false</d2p1:HasClientError>
<d2p1:HasServerError>false</d2p1:HasServerError>
<d2p1:HasWarningError>false</d2p1:HasWarningError>
<d2p1:Warnings xmlns:d4p1="http://schemas.microsoft.com/2003/10/Serialization/Arrays">
<d4p1:string>String</d4p1:string>
</d2p1:Warnings>
</d2p1:BhWorkflowComponentDto>
</components>
<hasClientError>false</hasClientError>
<hasServerError>false</hasServerError>
<hasWarningError>false</hasWarningError>
<isValid>false</isValid>
<outputs xmlns:d2p1="http://schemas.datacontract.org/2004/07/BH.API.DataAccess.Pipeline">
<d2p1:BhWorkflowOutputDto>
<d2p1:name>String</d2p1:name>
<d2p1:value>String</d2p1:value>
</d2p1:BhWorkflowOutputDto>
</outputs>
<warningErrors>String</warningErrors>
<workflowId>0</workflowId>
</FormBuilderMembershipPipelineRs>