https://linen.dev logo
API keys can access all Organization resources
# 🖥│support-forum
p
Hey team! I might be using it wrong, but it looks like Project API keys behave like Org keys. Using a Project-scoped API key created via
/api_keys/create
, I can hit org-wide endpoints and see data outside the key’s project. For example: List all Organization API keys:
Copy code
curl https://backend.composio.dev/api/v3/org/project/aaaaaaa/api_keys/list -H "x-api-key: <project_api_key>"
List all Organization team members:
Copy code
curl https://backend.composio.dev/api/v3/team-members/list -H "x-api-key: <project_api_key>"
Expected: Project API keys are constrained to that project Actual: Calls succeed and return org-wide data. Is this intended scope, or does it look like a scoping/security bug? Do you have any immediate mitigation advice in the meantime? Thanks!
c
Hello sorry for the inconvenience! So if you are an old Composio account, we didn't have the organisation->project hierarchy, thus the key created then can be accepted as organisation id. This will not reproduce with new accounts/projects/organisations. To mitigate this we have a flag we can set on our end if you don't want this to key to work this way. Please let us know.
l
Do you need developer?