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 .jsv suffix or ?format=jsv
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: text/jsv
Content-Type: text/jsv
Content-Length: length
{
batchFileDefinitionId: 0,
hotlistLineAppenderId: 0,
hotlistLineAppenderMap:
{
batchFileDefinitionId: 0,
batchFileDefinitionHotlistLineAppenderId: 0,
dateCreated: 0001-01-01
}
}