Multiple API Keys with Granular Access Control for Endpoints and Tasks

I would like to be able to create multiple API keys and configure access permissions on a per-endpoint or per-task basis.

Currently, there is only one API key per project, but from a security perspective, it would be much better to be able to create and distribute API keys with permissions limited to specific tasks only when integrating with external systems via API.

This feature would allow us to follow the principle of least privilege by granting minimal necessary access rights to each external integration, thereby improving overall security posture.