# Schema Registry ACL Management API or Programmatic Interface in Confluent for Kubernetes

**URL:** <https://forum.confluent.io/t/schema-registry-acl-management-api-or-programmatic-interface-in-confluent-for-kubernetes/35689>\
**Category:** Schema Registry\
**Created:** [16 January 2025 03:21 UTC](https://forum.confluent.io/t/schema-registry-acl-management-api-or-programmatic-interface-in-confluent-for-kubernetes/35689 "2025-01-16T03:21:14Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![msamar4](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.confluent.io/msamar4/32/4642_2.png) [@msamar4](https://forum.confluent.io/u/msamar4)\
**Post date:** [16 January 2025 03:21 UTC](https://forum.confluent.io/t/schema-registry-acl-management-api-or-programmatic-interface-in-confluent-for-kubernetes/35689/1 "2025-01-16T03:21:14Z")

</div>

We’re implementing automated Schema Registry ACL management in our Kubernetes environment using Confluent for Kubernetes (CFK). We need to programmatically create/manage Schema Registry ACLs.

Currently, we can only find documentation for managing Schema Registry ACLs via the **CLI (sr-acl-cli)**. However, for our Kubernetes automation, we need either:

1. A REST API endpoint for Schema Registry ACL management
2. Any other programmatic way to manage these ACLs

Could you confirm if any of these options exist? If not, what would be the recommended approach for automating Schema Registry ACL management in a Kubernetes environment?