BootView WebApi

<back to all web services

UpdateCustomerBatchFileDefinition

The following routes are available for this service:
PUT/customers/{customerId}/batchfiledefinitions/{id}Updates an existing batch file definition for a given customer. Fails if this user does not have access to this customer or if the batch file definition doesn't exist.
UpdateCustomerBatchFileDefinition Parameters:
NameParameterData TypeRequiredDescription
CustomerIdpathGuidYesThe Customer Id.
IdpathintYesThe Batch File Definition Id.
BatchTypeIdbodyintYesThe Batch Type Id.
BatchFileTypeIdbodyintYesThe Batch File Type Id.
BatchFileLayoutTypeIdbodyintYesThe Batch File Layout Type Id.
NamebodystringYesThe name of the batch file definition.
FileNamebodystringYesThe file name of the batch file definition.
FolderbodystringYesThe folder of the batch file definition.
DelimiterbodyintNoThe delimiter used in the batch file definition.
DateCreatedbodyDateTimeNoThe date/time the definition was created.
CreatedByIdbodyGuidNoThe creator of the batch file definition.
IsActivebodyboolYesWhether the batch file definition is active or not.
HotlistLineAppenderIdbodyintNoThe hotlist line appender id.
BatchFileDefinitionFieldsbodyList<CustomerBatchFileDefinitionField>NoAn array of objects representing the fields of the batch file definition.
ScofflawImportProcessIdbodyintYesThe Scofflaw Batch Process Type Id.
BatchFileQueryFilterbodyCustomerBatchFileQueryFilterNoAn object containing batch file query filters.
CustomerBatchFileDefinitionField Parameters:
NameParameterData TypeRequiredDescription
IdformintNo
BatchFileDefinitionIdformintNo
NameformstringNo
DescriptionformstringNo
LengthformintNo
QuotedformboolNo
FieldIndexformintNo
CreatedByIdformGuidNo
DateCreatedformDateTimeNo
BatchFileDefinitionFieldConvertersformList<BatchFileDefinitionFieldConverter>No
FieldValueLiteralformstringNo
BatchFileActualColumnTypeIdformint?No
BatchFileDefinitionFieldConverter Parameters:
NameParameterData TypeRequiredDescription
IdformintNo
NameformstringNo
ClassNameformstringNo
DescriptionformstringNo
CustomerBatchFileQueryFilter Parameters:
NameParameterData TypeRequiredDescription
IdformintNo
BatchFileIdformintNo
HasPayCreditCCformboolNo
HasPayCashCPformboolNo
HasPayDebitDCformboolNo
HasPayCheckingECformboolNo
HasPayECashformboolNo
HasFineParking3formboolNo
HasFinePropertyTax12formboolNo
HasFineRedLight13formboolNo
HasFineSpeeding23formboolNo

To override the Content-type in your clients, use the HTTP Accept Header, append the .jsv suffix or ?format=jsv

HTTP + JSV

The following are sample HTTP requests and responses. The placeholders shown need to be replaced with actual values.

PUT /customers/{customerId}/batchfiledefinitions/{id} HTTP/1.1 
Host: api.paylock.com 
Accept: text/jsv
Content-Type: text/jsv
Content-Length: length

{
	id: 0,
	batchTypeId: 0,
	batchFileTypeId: 0,
	batchFileLayoutTypeId: 0,
	name: String,
	fileName: String,
	folder: String,
	delimiter: 0,
	dateCreated: 0001-01-01,
	isActive: False,
	hotlistLineAppenderId: 0,
	batchFileDefinitionFields: 
	[
		{
			id: 0,
			batchFileDefinitionId: 0,
			name: String,
			description: String,
			length: 0,
			quoted: False,
			fieldIndex: 0,
			dateCreated: 0001-01-01,
			batchFileDefinitionFieldConverters: 
			[
				{
					id: 0,
					name: String,
					className: String,
					description: String
				}
			],
			fieldValueLiteral: String,
			batchFileActualColumnTypeId: 0
		}
	],
	scofflawImportProcessId: 0,
	batchFileQueryFilter: 
	{
		id: 0,
		batchFileId: 0,
		hasPayCreditCC: False,
		hasPayCashCP: False,
		hasPayDebitDC: False,
		hasPayCheckingEC: False,
		hasPayECash: False,
		hasFineParking3: False,
		hasFinePropertyTax12: False,
		hasFineRedLight13: False,
		hasFineSpeeding23: False
	}
}
HTTP/1.1 200 OK
Content-Type: text/jsv
Content-Length: length

0