Planned for
Content Management API: new `fields._displayField` selector for entries
Starting May 21st, 2026, the Content Management API supports a new token, fields._displayField, in the select= query parameter on GET /spaces/{space_id}/environments/{environment_id}/entries. When the token is included, the API resolves each entry's display field from its content type and returns the value under the field's real name.
The token is composable with the standard select operator: combine it with any other tokens you would normally pass to select=, or use it on its own. Unlike standard field selectors, fields._displayField does not require content_type=, so it can resolve the display field across entries from different content types in a single call.
Examples
select=fields._displayFieldreturns the resolved display field for each entry.select=sys,fields._displayFieldreturnssysplus the resolved display field for each entry.select=fields.body,fields._displayFieldcombined withcontent_type=returns the explicit field, and the resolved display field. The display field is not duplicated if it already appears in the select list.select=sys,fields,fields._displayFieldreturns the full entry. The token is a no-op when the barefieldsselector is present.
Entries whose content type has no displayField, or whose display field has no value, are returned without fields.
This change is additive. Existing select= behavior is unchanged.