The number of active downloads.
Whether or not this package has been archived by the user. If user_package only.
Float. User Packages.
Whether or not there is a BCC list. If user_package only.
How many bytes have been transferred.
Whether or not the package is fully available on the transfer node; when the package is complete, all transfers of the designated files and folders into the package have been successful and all designated files and folders are present on the node.
The timestamp that indicates when the package is complete. Refer to 'complete'.
The time at which package content will expire according to configured expiration policies. Refer to 'content_retention_duration' and to the related parameters 'delete_after_download' and 'delete_package_content_after_download_duration'.
When a time-based content expiration value is set for this package, the duration to retain packages contents. When this duration passes, the packages contents are deleted. Valid values are null - 10 years. Units are seconds.
The file ID on the node that contains package contents.
The timestamp for when this package was created.
Whether or not an expiration policy applies to this package, indicating that package contents will expire (be deleted) after all recipients have downloaded the package.
If 'delete_after_download' is set to 'true', this parameter configures an optional 'grace period', during which the package contents will be retained even after all recipients have downloaded the package. The timer for this setting begins when all recipients have downloaded the package; when the timer expires, the package contents are deleted. Valid values are null - 10 years. Units are seconds.
Whether or not package contents have been deleted, either by the sender, by an administrator, or by configured expiration policies.
Whether or not package contents were deleted by a download-based expiration policy.
The timestamp for the deletion of package contents.
Whether or not the deleted package was deleted by an administrator.
The ID of the user who deleted the package.
Whether or not the package is in draft status.
The time the draft expired/expires.
Whether or not the package has encryption_at_rest applied.
The reason for expiration. Package can be deleted by an administrator or by the sender, or can be deleted as a result of a configured time-based or download-based expiration policy.
Whether or not the package contents are expired due to a configured expiration policy.
The time the package expired/expires.
Whether or not the transfer of this package failed.
The number of failed downloads of this package; download attempts may be full (the entire package) or partial (some contents of the package).
The number of files included in this package. This counts individual files included in the package, not files that are contents of folders that are included in the package.
Whether or not the file_count value was obtained from the storage.
The ID for the file comprising all package contents.
The number of files that have completed transferring.
Number (obtained directly from the node) of files expected to be transferred as part of the package.
The number of folders actually included in this package per the transfer session. This counts individual folder included in the package, not folders that are nested within other folders that are included in the package. This value may or may not match the value for folders_expected.
Number (obtained directly from the node) of folders successfully transferred as part of the package.
Number (obtained directly from the node) of folders expected to be transferred as part of the package.
The number of full downloads completed for this package. This counts the times that recipients have downloaded the package as a whole, rather than partial downloads, when a recipient downloads individual files or folders of a package.
Whether or not the package has contents. If content has been deleted, either by the user, by an administrator, or as the result of configured package expiration policies, the package record remains accessible, but the package content has been deleted from the transfer server and cannot be recovered.
The ID for the package.
A metadata schema is used to present a form to a user when the user is submitting content to a dropbox. It is an array with "Field" objects, and each Field object defines one field that the user can fill out when submitting content to a dropbox. Note that the order of the fields in the metadata schema array will be the order in which they are shown to the user.
Package name.
The ID of the node that contains the package.
The sender's message to recipients to include with the package. Maximum characters: 65535.
Whether or not the package was read. If user_package only.
When the package was recalled.
Whether or not the package was received. If user_package only.
Whether or not the package was sent.
The timestamp for when the package was sent.
Whether or not all the contents of this package originate from the same location (node, workstation, etc.). When the package recipient downloads a package with Encryption at Rest (EAR) applied by the sender or by workspace configuration, and all package contents are from the same source (for example, the sender's desktop; a specific remote server), AoC signals Aspera Connect to prompt the recipient to apply the passphrase created by the sender and decrypt package contents during the download operation. When package contents are from disparate sources, previous behavior applies: the recipient applies the password to individual files in the downloaded package when opening each file.
The cumulative size of all the files and folders in the package.
The time remaining to complete an in-progress transfer. Float.
The number of transfer sessions expected to bring all package contents to the node supporting the workspace in which the package is sent. The number corresponds to the number of discrete source locations of the designated package contents. For example, if the package includes 20 files and folders from 5 discrete sources, the number of transfers expected is 5.
When the package was updated.
Whether or not the upload of the package has started.
The timestamp for when the package upload began.
If true, the package is watermarked
Watermarking configuration details
Percentage progress of the watermarking job
Status of the watermarking job. Allowable values:"COMPLETE", "IN_PROGRESS", "PENDING", "ERROR".
ID of the workspace from which this package was sent
PackagesResponse