5.3 Drop-Off for Batch Exception Handler

This service was created to handle structured batch files where each record is a separate transaction against the target system. Use the service to post aggregated exception information back to Thru MFT. Information can include exception messages and records which caused the exceptions. The size of the returned exception data is limited to 10MB per call. The rest is truncated.

ContentDisposition filename should have the following format: "TransportBatchExceptions.txt"

Method	Request Url
POST	api/TransportMgr/FlowDropOffChunk/<Flow Code>

Type	Parameter	Values
HEAD MULTIPARTHEAD MULTIPARTHEAD MULTIPARTHEAD POST	Authorization ContentDisposition: name ContentDisposition: filename ContentDisposition: size	<TransportMgrAuthHeader> "file" "TransportBatchExceptions.txt" int (Chunk size)
URL_PARAM	Flow Code	String (TRN…)

Status	Response	Note
200		Success
403	Content contains access denied message	Invalid Authorization Header in API call. Flow Code parameter in Transport does not match the Flow Code in Authorization header
500	Content contains exception (message and stack trace)	Failed to find the flow, chunk upload failed, end of file processing failed