Facebook Graph API限制 [英] Facebook Graph API limit

问题描述

我进行了研究，得出的结论是，Facebook Graph API的限制是每个访问令牌每600秒 600个请求 .

I have researched and I am on the conclusion that Facebook Graph API limits are 600 requests per 600 sec per access token.

并且由于我仅使用新的Graph API，所以我从未遇到过手动传递访问令牌的需要.我相信需要继续使用旧的REST API.这应该意味着，对于我的应用程序的每个不同用户，我都有一个不同的访问令牌，并且重置了我接下来600秒的API限制.谁能确认?

And since I am using the new Graph API only, I have never encounter the need of passing an access token manually. I believe one needs to pass on with the old REST API. It should mean that with every different user of my app, I have a different access token and my API limit for the next 600 secs is reset. Can anyone confirm?

如果我使用 offline_access 权限怎么办?我在某处读到，具有offline_access许可的访问令牌永远不会更改，因此您可以随时访问数据.真的?那么在这种情况下，对于该访问令牌，我的请求速率仅为600个请求/600秒.正确吗?

What if I am using offline_access permission? I read somewhere that with offline_access permission the access token never changes and hence you can access data any time. True? Then in this case I just have the rate of 600 requests / 600 sec for this access token. Correct?

我正在构建一个我相信会流行的应用程序，所以我试图不被API使用限制.一次访问(它完全可以在AJAX上使用)，我每个用户使用10-15个查询，因此考虑到速率，我远低于可以使用FB API的速率吗?

I am building an app that I believe will go viral, so I am trying not to be blocked out of my API usage. On a visit (it totally works on AJAX), I use 10-15 queries per user, so considering the rate, I am much below the rate at which I can use FB API?

因此，作为一个整体，我的应用程序可能有100万用户，这使我可以同时为每个用户的访问令牌执行600个请求/600秒.

So as a whole, I may have a million users for my app, letting me to do 600 requests / 600 sec for each user's access token, all simultaneously.

任何人都可以发表评论吗?

Can anyone please comment?

推荐答案

API速率限制主要基于使用该应用程序的用户数量.因此，随着应用程序的普及度增加，您可以进行的API调用总数也会增加.在正常使用率下，限制不应该成为问题.专注于基于每个用户的效率.

API rate limits are primarily based on the number of users using the application. So as your app's popularity increases the total number of API calls you can make also increases. Under normal usage rate limits should not be an issue. Focus on being efficient on a per-user basis.

注意:不建议使用offline_access-但很容易刷新用户令牌: https://developers.facebook.com/roadmap/offline-access-removal/

Note: offline_access is being deprecated - but it is easy to refresh user tokens: https://developers.facebook.com/roadmap/offline-access-removal/

这篇关于Facebook Graph API限制的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！