Unfortunately, not at this point in time. That endpoint is used to list every entitlement feature available in the current pod so it seems unlikely to be used in an automation context. Maybe you can elaborate on the workflow you are trying to achieve and file it as a feature request on the BDK repo. https://github.com/finos/symphony-bdk-java/issues What is available is the user features endpoint, available via `userService.getFeatureEntitlements(long userId)` as well as the ability to update it via `userService.updateFeatureEntitlements(long userId, List<Feature> features)`. You can choose to implement this yourself using a [BDK Extension](https://symphony-bdk-java.finos.org/extension.html). Here's a quick example: ``` java public class BotApplication { public static void main(String[] args) throws Exception { final SymphonyBdk bdk = new SymphonyBdk(loadFromClasspath("/config.yaml")); bdk.extensions().register(FeaturesExt.class); List<String> featuresList = FeaturesExt.listFeatures(); System.out.println(String.join(",", featuresList)); } } ``` ```java public class FeaturesExt implements BdkExtension, BdkApiClientFactoryAware, BdkAuthenticationAware { private static AuthSession authSession; private static ApiClient apiClient; public void setAuthSession(AuthSession a) { authSession = a; } public void setApiClientFactory(ApiClientFactory a) { apiClient = a.getPodClient("/pod"); } public static List<String> listFeatures() throws ApiException { String path = "/v1/admin/system/features/list"; String json = "application/json"; Map<String, String> headers = Map.of("sessionToken", authSession.getSessionToken()); TypeReference<List<String>> type = new TypeReference<>() {}; ApiResponse<List<String>> response = apiClient.invokeAPI(path, "GET", null, null, headers, null, null, json, json, null, type); if (response.getStatusCode() != 200) { throw new ApiException(response.getStatusCode(), "Error"); } return response.getData(); } } ```

Unfortunately, not at this point in time. That endpoint is used to list every entitlement feature available in the current pod so it seems unlikely to be used in an automation context. Maybe you can elaborate on the workflow you are trying to achieve and file it as a feature request on the BDK repo. https://github.com/finos/symphony-bdk-java/issues What is available is the user features endpoint, available via `userService.getFeatureEntitlements(long userId)` as well as the ability to update it via `userService.updateFeatureEntitlements(long userId, List<Feature> features)`.