This service is used to send packages that have been created from files on a remote source. Same as the send-to-service, except a remote file source and paths need to be specified. Unlike the send-to-service, calling send will actually initiate an upload from the remote source to faspex. The response only indicates the success/failure of transfer initiation, not the result of the upload.
- Supported Formats: JSON
- faspex Support: 3.0 +
Below is an example of a Request in JSON format, the source ID is only needed if sending a package from a remote file source. Specifying paths without a source ID will prepare a local upload from the client’s computer. Although the API allows specifying multiple sources for one package, this will be initially unsupported. The current syntax allows for future expansion.
It is important to note that when sending to a Dropbox the dropbox must be the only recipient or an error will be returned stating 'Package creation failed' with an internal message of 'Dropbox recipient must be the only recipient.'
Additional JSON fields that can be enabled server-side by an admin include "delete_after_download"; which could then allow you to specify 0 for do nothing, 1 for delete after all recipients download all of the files, or 2 for delete after any recipients downloads all of the files. Additional options like "notify_on_[download/upload]" and "notifiable_on_[download/upload]" can be used together for setting notification policies.
The response for a package submitted from a local client browser is basically a passthrough of the Node API response, with the addition of a generated fasp URL for convenience. A submission from a remote source will not include the xfer_sessions key; rather, only a link to the package status.