# Error 403 when trying to list created plugins in CloudQuery **URL:** \ **Category:** CloudQuery Plugins\ **Created:** [April 16, 2024, 9:23pm UTC](https://community.cloudquery.io/t/error-403-when-trying-to-list-created-plugins-in-cloudquery/251 "2024-04-16T21:23:44Z")\ **Posts on this page:** 15\ **Page:** 1
**Author:** ![first-bullfrog](https://avatars.discourse-cdn.com/v4/letter/f/e95f7d/32.png) [@first-bullfrog](https://community.cloudquery.io/u/first-bullfrog)\ **Post date:** [April 16, 2024, 9:23pm UTC](https://community.cloudquery.io/t/error-403-when-trying-to-list-created-plugins-in-cloudquery/251/1 "2024-04-16T21:23:44Z")
Hi, I have created a Google Calendar plugin and published it to CQ Cloud as private. Now, I want to get the list of all the plugins I’ve created, but I’m getting a `403` in the API call response. Feel free to help with the solution, possible reasoning, or any questions that you have around this issue. ---
**Author:** ![ben](https://sea1.discourse-cdn.com/flex001/user_avatar/community.cloudquery.io/ben/32/88_2.png) [@ben](https://community.cloudquery.io/u/ben)\ **Post date:** [April 16, 2024, 9:34pm UTC](https://community.cloudquery.io/t/error-403-when-trying-to-list-created-plugins-in-cloudquery/251/2 "2024-04-16T21:34:44Z")
Are you using an API key to authenticate your API call? More information about how to generate an API key can be found [here](https://docs.cloudquery.io/docs/deployment/generate-api-key). You should be able to use the API key as a Bearer auth token to authenticate. ---
**Author:** ![striking-glider](https://avatars.discourse-cdn.com/v4/letter/s/f6c823/32.png) [@striking-glider](https://community.cloudquery.io/u/striking-glider)\ **Post date:** [April 16, 2024, 11:20pm UTC](https://community.cloudquery.io/t/error-403-when-trying-to-list-created-plugins-in-cloudquery/251/3 "2024-04-16T23:20:58Z")
@ben I’m getting the same result on my end as well - we’re passing the API key generated from the team settings page as a bearer token, but any endpoints that are scoped to a single team respond with a 403. We’re also able to call the `ListTeams` endpoint, and our team is returned as the only item in the list. ---
**Author:** ![ben](https://sea1.discourse-cdn.com/flex001/user_avatar/community.cloudquery.io/ben/32/88_2.png) [@ben](https://community.cloudquery.io/u/ben)\ **Post date:** [April 16, 2024, 11:50pm UTC](https://community.cloudquery.io/t/error-403-when-trying-to-list-created-plugins-in-cloudquery/251/4 "2024-04-16T23:50:31Z")
We will take a look and get back to you! ---
**Author:** ![erez](https://sea1.discourse-cdn.com/flex001/user_avatar/community.cloudquery.io/erez/32/40_2.png) [@erez](https://community.cloudquery.io/u/erez)\ **Post date:** [April 17, 2024, 9:42am UTC](https://community.cloudquery.io/t/error-403-when-trying-to-list-created-plugins-in-cloudquery/251/5 "2024-04-17T09:42:12Z")
Hi 👋 We had an access control bug in our backend related to API keys and listing plugins. A fix has been rolled out, can you try again? ---
**Author:** ![first-bullfrog](https://avatars.discourse-cdn.com/v4/letter/f/e95f7d/32.png) [@first-bullfrog](https://community.cloudquery.io/u/first-bullfrog)\ **Post date:** [April 17, 2024, 10:50am UTC](https://community.cloudquery.io/t/error-403-when-trying-to-list-created-plugins-in-cloudquery/251/6 "2024-04-17T10:50:33Z")
Hi @erez, Thank you for looking into it. The API that I had listed is working now. But the issue still persists in other APIs. I have attached a couple of screenshots for your reference. ---
**Author:** ![erez](https://sea1.discourse-cdn.com/flex001/user_avatar/community.cloudquery.io/erez/32/40_2.png) [@erez](https://community.cloudquery.io/u/erez)\ **Post date:** [April 17, 2024, 11:03am UTC](https://community.cloudquery.io/t/error-403-when-trying-to-list-created-plugins-in-cloudquery/251/7 "2024-04-17T11:03:06Z")
Are you able to list teams (e.g. `/teams`)? Please note an API key has access only to a single team (the one it was created under). So you shouldn’t be able to create a new team using it or get a specific team. For cross-team operations, you should use the `cloudquery login` token. ---
**Author:** ![pilvikala](https://sea1.discourse-cdn.com/flex001/user_avatar/community.cloudquery.io/pilvikala/32/11_2.png) [@pilvikala](https://community.cloudquery.io/u/pilvikala)\ **Post date:** [April 17, 2024, 11:23am UTC](https://community.cloudquery.io/t/error-403-when-trying-to-list-created-plugins-in-cloudquery/251/8 "2024-04-17T11:23:36Z")
@first-bullfrog Could you tell us a bit more about what you are trying to achieve with creating a team via API? ---
**Author:** ![first-bullfrog](https://avatars.discourse-cdn.com/v4/letter/f/e95f7d/32.png) [@first-bullfrog](https://community.cloudquery.io/u/first-bullfrog)\ **Post date:** [April 17, 2024, 12:09pm UTC](https://community.cloudquery.io/t/error-403-when-trying-to-list-created-plugins-in-cloudquery/251/9 "2024-04-17T12:09:14Z")
Yes, I am able to list teams! @pilvikala: The idea is to use teams similarly as Airbyte workspaces. Thus creating a logical segmentation for the same set of source and destination syncs for different users. Hope this answers your question. ---
**Author:** ![pilvikala](https://sea1.discourse-cdn.com/flex001/user_avatar/community.cloudquery.io/pilvikala/32/11_2.png) [@pilvikala](https://community.cloudquery.io/u/pilvikala)\ **Post date:** [April 17, 2024, 12:42pm UTC](https://community.cloudquery.io/t/error-403-when-trying-to-list-created-plugins-in-cloudquery/251/10 "2024-04-17T12:42:13Z")
@first-bullfrog Thank you for the explanation! @first-bullfrog At the moment, we have a limit of 3 teams per user. If you need more, it would be great if we could meet and discuss your use case a bit more in detail and see how we can support you. Let me know if you’d like to chat and I can send a calendar link. ---
**Author:** ![first-bullfrog](https://avatars.discourse-cdn.com/v4/letter/f/e95f7d/32.png) [@first-bullfrog](https://community.cloudquery.io/u/first-bullfrog)\ **Post date:** [April 17, 2024, 2:13pm UTC](https://community.cloudquery.io/t/error-403-when-trying-to-list-created-plugins-in-cloudquery/251/11 "2024-04-17T14:13:10Z")
@pilvikala: Got it! We surely can get on a call. Let me share a couple of follow-up questions and then we can decide if the call is still required. 1. Is this limitation only applicable for CQ Cloud or is it applicable for the self-hosted instances too? 2. I am also trying to create a sync source using the private plugin I’ve published to CQ Cloud, but I’m getting a 404. Is this a restriction too? (Can I not create a sync source using my private plugin?) ---
**Author:** ![pilvikala](https://sea1.discourse-cdn.com/flex001/user_avatar/community.cloudquery.io/pilvikala/32/11_2.png) [@pilvikala](https://community.cloudquery.io/u/pilvikala)\ **Post date:** [April 18, 2024, 8:30am UTC](https://community.cloudquery.io/t/error-403-when-trying-to-list-created-plugins-in-cloudquery/251/12 "2024-04-18T08:30:33Z")
@first-bullfrog The CQ Cloud manages team memberships, and when you are running a sync locally, you need to authenticate with the Cloud (for billing purposes). So yes, it is applicable to self-hosted instances. As for using private plugins in the Cloud, we have decided not to allow that until we actually get some feedback from our customers. This is to prevent the abuse of our infrastructure. We’re happy to discuss this on a case-by-case basis. ---
**Author:** ![first-bullfrog](https://avatars.discourse-cdn.com/v4/letter/f/e95f7d/32.png) [@first-bullfrog](https://community.cloudquery.io/u/first-bullfrog)\ **Post date:** [April 18, 2024, 1:25pm UTC](https://community.cloudquery.io/t/error-403-when-trying-to-list-created-plugins-in-cloudquery/251/13 "2024-04-18T13:25:18Z")
@pilvikala: Understood. Is private plugin usage blocked in the self-hosted instance too? Or can we create syncs, sources, and syncs there? ---
**Author:** ![pilvikala](https://sea1.discourse-cdn.com/flex001/user_avatar/community.cloudquery.io/pilvikala/32/11_2.png) [@pilvikala](https://community.cloudquery.io/u/pilvikala)\ **Post date:** [April 18, 2024, 1:25pm UTC](https://community.cloudquery.io/t/error-403-when-trying-to-list-created-plugins-in-cloudquery/251/14 "2024-04-18T13:25:46Z")
No, you can use private plugins on your own infrastructure. ---
**Author:** ![first-bullfrog](https://avatars.discourse-cdn.com/v4/letter/f/e95f7d/32.png) [@first-bullfrog](https://community.cloudquery.io/u/first-bullfrog)\ **Post date:** [April 18, 2024, 1:26pm UTC](https://community.cloudquery.io/t/error-403-when-trying-to-list-created-plugins-in-cloudquery/251/15 "2024-04-18T13:26:23Z")
Thanks for the clarification.