The Assets HTTP API allows for create-read-update-delete (CRUD) operations on digital assets, including on metadata, on renditions, and on comments, together with structured content using Experience Manager Content Fragments. It is exposed at /api/assets and is implemented as REST API. It includes support for Content Fragments.
To access the API:
Open the API service document at https://[hostname]:[port]/api.json.
Follow the Assets service link leading to https://[hostname]:[server]/api/assets.json.
The API response is a JSON file for some MIME types and a response code for all MIME types. The JSON response is optional and may not be available, for example for PDF files. Rely on the response code for further analysis or actions.
After the Off Time, an asset and its renditions are not available via the Assets web interface and through the HTTP API. The API returns 404 error message if the On Time is in the future or Off Time is in the past.
HTTP API updates the metadata properties in the jcr namespace. However, the Experience Manager user interface updates the metadata properties in the dc namespace.
A content fragment is a special type of asset. It can be used to access structured data, such as texts, numbers, dates, amongst others. As there are several differences to standard assets (such as images or documents), some additional rules apply to handling content fragments.
For further information see Content Fragments Support in the Experience Manager Assets HTTP API.
The Assets HTTP API exposes two major elements, folders and assets (for standard assets).
Additionally, it exposes more detailed elements for the custom data models that describe structured content in Content Fragments. See Content Fragment Data Models for further information.