BootView WebApi

UpdateMergeHistory

The following routes are available for this service:
PUT	/collectionattemptmerge/{id}	Updates items in a collection attempt with items merged from another collection attempt

**UpdateMergeHistory** Parameters:
Name	Parameter	Data Type	Required	Description
Id	path	Guid	Yes	The id of the source from which the item is being merged.
MergeItemType	body	MergeType	Yes	Type of item being merged
MergeTargetType	body	MergeType	Yes	Type of item being merged to
MergeTargetFromId	body	Guid	Yes	The id of the target to which the item is being merged.
MergeTargetToId	body	Guid	Yes	The id of the target to which the item is being merged.
MergeItemIds	body	List<Guid>	Yes	A list of bill ids that are being merged

**MergeType** Enum:
Unknown
Bill
Payment
Note
Collection

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.

PUT /collectionattemptmerge/{id} HTTP/1.1 
Host: api.paylock.com 
Accept: application/xml
Content-Type: application/xml
Content-Length: length

<UpdateMergeHistory xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/BootView.WebApi.ServiceModel">
  <Id>00000000-0000-0000-0000-000000000000</Id>
  <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>
</UpdateMergeHistory>

HTTP/1.1 200 OK
Content-Type: application/xml
Content-Length: length

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