Asset entities are used primarily in App Services to manage binary data objects such as images, video, and audio content. However, an asset does not have to be used for a binary object. For example, assets can be used to model a file system.
Using App services APIs you can create, retrieve, update, delete, and query asset entities. See General-purpose endpoints for descriptions of these APIs.
The following are the system-defined properties for asset entities. You can create application-specific properties for an asset entity in addition to the system-defined properties. The system-defined properties are reserved. You cannot use these names to create other properties for an asset entity. In addition the assets name is reserved for the assets collection — you can't use it to name another collection.
|uuid||UUID||Asset’s unique entity ID|
|name||string||Asset name (mandatory)|
|created||long||UNIX timestamp of entity creation|
|modified||long||UNIX timestamp of entity modification|
|owner||UUID||UUID of the asset’s owner (mandatory)|
|path||string||Relative path to the asset (mandatory)|
|content-type||string||Content type of the asset (for example, “image/jpeg”)|
Assets have the following set property.
|connections||string||Set of connections for the asset|