Resolved entries

Entries can be resolved automatically to a maximum depth of 10 using the linkDepth or fieldLinkDepths parameter in any retrieval operation. Being able to resolve entries in a single HTTP call can significantly improve the render performance of your webpage or application. Whilst fewer network requests can be beneficial, it can also be detrimental if the linkDepth in particular is too deep or where there are many link fields. In such cases, it is more efficient to specify individual fieldLinkDepths.

Field-specific link depths:

From version 16 of Contensis onwards, if you want to specify link depths for individual fields, you can use the fieldLinkDepths querystring parameter on all Delivery API search endpoints. This is a simple 'dictionary' of field paths and link depth values. Matching field paths override the link depth and where more than one field path matches a field, the most specific (longest) is used. This example will resolve to a link depth of 1 for all fields, except for the composer field which is resolved to a link depth of 2, though the entryLink field in a linkedEntryComponent in that composer is overridden to return to a link depth of 1.

Linked content

Still need help?