BootView WebApi

<back to all web services

CreateMergeHistory

The following routes are available for this service:
POST/collectionattemptmergeCreates items in a collection attempt with items merged from another collection attempt
CreateMergeHistory Parameters:
NameParameterData TypeRequiredDescription
MergeItemTypebodyMergeTypeYesType of item being merged
MergeTargetTypebodyMergeTypeYesType of item being merged to
MergeTargetFromIdbodyGuidYesThe id of the target to which the item is being merged.
MergeTargetToIdbodyGuidYesThe id of the target to which the item is being merged.
MergeItemIdsbodyList<Guid>YesA list of bill ids that are being merged

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 /xml/reply/CreateMergeHistory HTTP/1.1 
Host: api.paylock.com 
Content-Type: application/xml
Content-Length: length

<CreateMergeHistory xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/BootView.WebApi.ServiceModel">
  <MergeItemIds xmlns:d2p1="http://schemas.microsoft.com/2003/10/Serialization/Arrays">
    <d2p1:guid>00000000-0000-0000-0000-000000000000</d2p1:guid>
  </MergeItemIds>
  <MergeItemType>Unknown</MergeItemType>
  <MergeTargetFromId>00000000-0000-0000-0000-000000000000</MergeTargetFromId>
  <MergeTargetToId>00000000-0000-0000-0000-000000000000</MergeTargetToId>
  <MergeTargetType>Unknown</MergeTargetType>
</CreateMergeHistory>
HTTP/1.1 200 OK
Content-Type: application/xml
Content-Length: length

<boolean xmlns="http://schemas.microsoft.com/2003/10/Serialization/">false</boolean>