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 //worship_options HTTP/1.1
Host: api.lsu.abodehms.com
Accept: application/xml
Content-Type: application/xml
Content-Length: length
<CreateWorshipOption xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/AbodeAPI.ServiceModel">
<AllowLimitOverride>false</AllowLimitOverride>
<Code>String</Code>
<Credits>0</Credits>
<DailyLimit>0</DailyLimit>
<DefaultTime>0001-01-01T00:00:00</DefaultTime>
<Description>String</Description>
<Name>String</Name>
<PresenterBonus>0</PresenterBonus>
<TermLimit>0</TermLimit>
<WeeklyLimit>0</WeeklyLimit>
<WorshipCategoryId>0</WorshipCategoryId>
</CreateWorshipOption>
HTTP/1.1 200 OK
Content-Type: application/xml
Content-Length: length
<WorshipOptionDTO xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/AbodeAPI.ServiceModel">
<AllowLimitOverride>false</AllowLimitOverride>
<Code>String</Code>
<Credits>0</Credits>
<DailyLimit>0</DailyLimit>
<DefaultTime>0001-01-01T00:00:00</DefaultTime>
<Description>String</Description>
<Name>String</Name>
<PresenterBonus>0</PresenterBonus>
<TermLimit>0</TermLimit>
<WeeklyLimit>0</WeeklyLimit>
<WorshipCategoryId>0</WorshipCategoryId>
<WorshipOptionId>0</WorshipOptionId>
</WorshipOptionDTO>