允许使用多个YouTube API键进行1个项目?
在使用YouTube数据API V3仅使用1个API键进行搜索时,我很快达到了配额限制。
我申请了配额增加,但我听说这可能需要一些时间。
但是,我登陆了以下文章,该文章指出,最多300个API可用于1个项目。我真的允许使用多个YouTube数据API V3键,并且每次达到配额限制时之间的切换?
https://cloud.google.com/docs/authentication/authentication/api-keys
我一直在争夺解决方案。我希望我读得很好!
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(2)
项目中的键和凭据共享其配额。在Google开发人员控制台上的同一项目中创建其他API键不会为您提供其他配额。
如下所示,她的所有证书将共享相同的配额。
您需要创建其他项目并在每个项目中创建一个密钥。
所有这些项目都具有自己的配额。
您应该等待延长,如今,不应该花费几周的时间才能回到配额增加。
Keys and credentials within a project share their quota. Creating additional api keys within the same project on google developer console is not going to get you additional quota.
As seen below all the credentials her will share the same quota.
You would need to create additional projects and create a key within each project.
All of these projects have their own credentials with their own quotas.
You should wait for an extension These days it shouldn't take more then a couple of weeks to hear back about a quota increase.
答案是肯定的,否(但在您的情况下可能比Yes 更否)。
是的,您可以使用多个YouTube数据API V3键,然后在之间切换,但不能在它们之间切换,因为您达到了配额限制。
通过这样做,您违反了YouTube的开发人员政策合规性,并使自己受到制裁。您应该在它们之间切换的唯一原因是将环境分开。
来自YouTube的开发人员政策:
来源:https://developers.google.com/youtube/terms/developer-policies-guide#don%E2%80%99t_spread_api_access_across_multiple_or_unknown_projects
The answer is yes and no (but probably more no than yes in your case).
YES, you are allowed to use multiple Youtube Data API v3 keys and switch between but NO, you can't switch between them because you reached the quota limitation.
By doing so, you violate Youtube's Developer Policies compliance and expose yourself to sanctions. The only reason you should switch between them is to separate your environments.
From the Youtube's Developer Policies :
source : https://developers.google.com/youtube/terms/developer-policies-guide#don%E2%80%99t_spread_api_access_across_multiple_or_unknown_projects