Assets are used to store an application's static resources, rather than the dynamic, record-specific data stored in object meta data. These static resources can include images, reference tables, configuration strings, or anything else that does not change. No authorization is required to read assets, so they are not to be used to store sensitive information.



The value of the asset can either be a JSON object or a binary file, such as an image. When creating or updating an asset, the desired JSON object or binary file is sent in the body of the PUT request.


The type of an asset is determined by its value. If an asset's value is a JSON object, its type is keyValue, and if an asset's value is a binary file, its type is file. Different types of binary files are not discriminated against.


The source of the asset refers to the origin of its data. The Droplit system contains a default group of assets whose source is master. These assets cannot be overwritten or overridden, but they can be copied and those copies may be modified. These modified copies, as well as new user-created assets, have a source of custom.

When modifying an asset of type keyValue, overwriting occurs at the top level of the JSON object. Properties whose values are objects will be completely overwritten rather than merely having their subproperties merged.