What to do and how to do?
In the JSON response of a successful query, linked items are placed in the includes
array, when not already fetched in the items
array.
Note: Links in the Delivery API will always only resolve to published entries. Unresolved items will not be present in the includes
array. The Preview API will include draft entries with the same caveat that unresolved links will not appear in the includes
array.
Assets are the binary files in a space. An asset can be any file type and are usually attached to entries with links.
You can localize assets by providing separate files for each locale. Assets which are not localized are available as a single file under the default locale.
When you query for entries which contain links to assets then all assets are included by default.
By default, a signed asset URL will stop functioning after the
expiresAt
value that was specified when creating the asset key. When generating the JWT, you may optionally specify anexp
(expiry) that will cause the signed URL to be unusable at the specified expiry time.
The locales endpoint returns a list of all created locales. One will have the flag default
set to true and is the locale used in the CDA, and you specified no other locale in the request.