By default, endpoints that retrieve and list entry data return all user attributes and no operational attributes (unless the server is configured to return specified operational attributes by default). The GET /directory/v1/{dn} endpoint also supports fine-tuning the response data through the following request parameters:

includeAttributes

Specifies the attribute or attributes in the entry that should be included in the response.
excludeAttributes

Specifies the attribute or attributes in the entry that should be excluded in the response.

These request parameters accept a comma-separated list of attributes to either include or exclude from the response entries. They also support the following aliases as values:

*

Refers to all user attributes of the resource.
_operationalAttributes

Refers to all operational attributes of the resource.

Note: If the same attribute is provided in both includeAttributes and excludeAttributes, an error is returned. When the * alias is used, the excludeAttributes parameter takes precedence. For example, includeAttributes=*&excludeAttributes=sn returns all user attributes except sn, but excludeAttributes=*&includeAttributes=sn returns no attributes (except DN).

The sample shows the GET /directory/v1/{dn} operation to return the base entry and all user attributes for the entry, but exclude sn.