5.1 File Pickup (Thru MFT to Flow)

Download (Pick-Up) file from Thru MFT Transport from any subscribing organizations.

Thru MFT API returns one file per request from the internal queue. iPaaS flow should call this method periodically / by scheduling. Note that Thru MFT scheduling takes precedence over the flow schedule – for example, the flow can be defined for 10 seconds but Thru MFT to 5 minutes. Thru MFT will only move a file from landing to pick up every 10 minutes, so in effect, files will become available to the flow every 10 minutes.

Method	Request Url
GET	api/TransportMgr/FlowPickup/<Flow Code>

Type	Parameter	Values
HEAD	Authorization	TransportMgrAuthHeader (Required in all service requests)
URL_PARAM	Flow Code	Transport Code (TRN…)

Status	Response	Note
200	Returns file content in raw format	MIME type, file name and size are in content disposition header.
	Additional information about the file can be retrieved from disposition header. Size can be retrieved from Content-Length header Example: Content-Disposition: attachment; filename="FL00000001-ChunkNumber000001" Thru MFT delivers the file with File Code prefix as shown above. This ensures the uniqueness of the file in case it needs to be persisted. The flow should strip the prefix when delivering the file to the target app.
204	Content is empty	No content: no files are available for a pickup. Note that Thru MFT implements caching for pickup and files from a single endpoint will be given (One at a time) every 10-15 seconds. If the flow is trying to pick up files every seconds and there are pending files, the API will still return 204 until the next file is loaded to the cache.
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 Transport, or physical file is missing (quarantined), or download streaming failed.