Waiting for engine...
Skip to main content

Downloading API URL parameters using a security token

note

sessionID from MFT FS is not required of this type of download, user is not authenticated in MFT FS since calling application is supposed to authenticate a user.

Required URL parameters:

  • ThruFiles: String of comma separated tokens for file for downloads, one token per file.
    For Security token format, refer to the Security Token topic. Multiple tokens are separated by comma.
<encrypted token in base64format>, < encrypted token2 in base64format > … < encrypted tokenN in base64format >
  • ThruApplicationID: API key configured for the integration, which creates a download link.
  • ThruSuccessUrl: The Browser window containing the download tool will be redirected to this URL on successful download.
  • ThruErrorReportingUrl: The Browser window containing the download tool will be redirected to this URL on a failed download.

If download failed, the server returns a server error code in the parameter ThruErrorCode.

If an error occurs and ThruErrorReportingURL is not defined, the server throws an exception on the page containing the Java download applet.

note

The value of ThruErrorReportingUrl is not validated. You should verify it is a valid URL that exists when integrating MFT FS download tool.

Sample URL with security token:

http:// [test.thrudownload.com](http://test.thrudownload.com/) /ExternalJavaDownload.aspx?ThruSuccessUrl=http://google.com&ThruErrorReportingUrl=http://y  
[ahoo.com](http://ahoo.com/)&ThruFiles=hLmrvNNh7rMjT%2ffLL27vyQDPXUl%2fUjBKKwurzLAxmopIxotP%2fT20Mz5  
J180jhG3Soqkz8bB1AV6rz3NMcyYtmm3mdo%2bCLeD0FDfgJZ6cw1Iqs9V%2bR79KsJ1mzfUKGrgQ  
mrOq1NlosLcBtzmoVPW4%2bCqkt%2bbkNBdYoYw8DITFkHd%2fVsEHCnk5pjPd89mDATyjTu4xM  
CXFVH20lP7tTOU75k61LLSj3×6bHzCuorKcUzp7nuvxve0se9cOdFQ3TA6XH78IMGmdoOz9JgDPITy  
z1Q%3d%3d&ThruApplicationID=2987490673892