Skip to main content

Individual team member API keys or ability to scope API keys

Feature Request

Hello!

Today I was attempting to connect my account to make.com

I have an owner admin account that manages profiles, and my personal profile as a second account with my own accounts scoped to it

I noticed my personal account could not see the API section, only the owner account can, and when creating an API key I cannot scope it to restrict the workspace.

It would be nice if the profile users themselves could create an API key, or, at least allow the account owner to scope the api key and restrict it to certain profiles

Posted by Dalek ·
Status: Completed3 comments

Log in to comment and vote

Comments3

  • Miquel Palet López

    Team•

    Jul 13

    Good news, scoped API keys are supported!

    When creating a key, set scope to "profiles" and pass profileIds to restrict that key to specific profiles only (default is "full" = all profiles). You can also set the permission level to read-write or read-only. This lets you hand out isolated, least-privilege keys per client or workspace.

    Details here: docs.zernio.com/api-keys/create-api-key. Thanks for the request!

  • Dalek

    •

    Feb 20

    This was complete as of February 18, 2026 , thank you so much!

  • Dalek

    •

    Jan 22

    Another thought I had on this would be that if we could scope out API keys per-user and allow them to use the profiles they have permissions for that would be neat too. Scoping api keys would be so nice, no need to expose profiles to the key if they will never be used on it anyways.