BootView WebApi

<back to all web services

UpdateCustomerHotlistLineAppender

The following routes are available for this service:
PUT/customers/{customerId}/batchfiledefinitions/{batchFileDefinitionId}/hotlistlineappender/{hotlistlineappenderid}Updates mapping for hotlist line appender to file definition.
UpdateCustomerHotlistLineAppender Parameters:
NameParameterData TypeRequiredDescription
CustomerIdpathGuidYesThe Customer Id.
BatchFileDefinitionIdpathintYesThe Batch File Definition Id.
HotlistLineAppenderIdpathintYesThe Hotlist Line Appender Map Id.
HotlistLineAppenderMapbodyCustomerHotlistLineAppenderMapYesA map between a hotlist line appender and file definition.
CustomerHotlistLineAppenderMap Parameters:
NameParameterData TypeRequiredDescription
BatchFileDefinitionIdformintNo
BatchFileDefinitionHotlistLineAppenderIdformintNo
CreatedByIdformGuidNo
DateCreatedformDateTimeNo

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

<UpdateCustomerHotlistLineAppender xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/BootView.WebApi.ServiceModel">
  <BatchFileDefinitionId>0</BatchFileDefinitionId>
  <CustomerId>00000000-0000-0000-0000-000000000000</CustomerId>
  <HotlistLineAppenderId>0</HotlistLineAppenderId>
  <HotlistLineAppenderMap>
    <BatchFileDefinitionHotlistLineAppenderId>0</BatchFileDefinitionHotlistLineAppenderId>
    <BatchFileDefinitionId>0</BatchFileDefinitionId>
    <CreatedById>00000000-0000-0000-0000-000000000000</CreatedById>
    <DateCreated>0001-01-01T00:00:00</DateCreated>
  </HotlistLineAppenderMap>
</UpdateCustomerHotlistLineAppender>