PUT | /customers/{customerId}/batchfiledefinitions/{batchFileDefinitionId}/hotlistlineappender/{hotlistlineappenderid} | Updates mapping for hotlist line appender to file definition. |
---|
Name | Parameter | Data Type | Required | Description |
---|---|---|---|---|
CustomerId | path | Guid | Yes | The Customer Id. |
BatchFileDefinitionId | path | int | Yes | The Batch File Definition Id. |
HotlistLineAppenderId | path | int | Yes | The Hotlist Line Appender Map Id. |
HotlistLineAppenderMap | body | CustomerHotlistLineAppenderMap | Yes | A map between a hotlist line appender and file definition. |
Name | Parameter | Data Type | Required | Description |
---|---|---|---|---|
BatchFileDefinitionId | form | int | No | |
BatchFileDefinitionHotlistLineAppenderId | form | int | No | |
CreatedById | form | Guid | No | |
DateCreated | form | DateTime | No |
To override the Content-type in your clients, use the HTTP Accept Header, append the .json suffix or ?format=json
To embed the response in a jsonp callback, append ?callback=myCallback
The following are sample HTTP requests and responses. The placeholders shown need to be replaced with actual values.
PUT /customers/{customerId}/batchfiledefinitions/{batchFileDefinitionId}/hotlistlineappender/{hotlistlineappenderid} HTTP/1.1
Host: api.paylock.com
Accept: application/json
Content-Type: application/json
Content-Length: length
{"customerId":"00000000000000000000000000000000","batchFileDefinitionId":0,"hotlistLineAppenderId":0,"hotlistLineAppenderMap":{"batchFileDefinitionId":0,"batchFileDefinitionHotlistLineAppenderId":0,"createdById":"00000000000000000000000000000000","dateCreated":"\/Date(-62135596800000-0000)\/"}}