Facebook Graph API限制了疑问 [英] Facebook Graph API limit doubt

问题描述

我在facebook开发论坛和对于现有的问题，我得出结论，Facebook Graph API限制是每次访问令牌每600秒600次请求 。

I have researched high and low everywhere on facebook dev forums & SO existing questions, and I am on the conclusion that Facebook Graph API limits are 600 requests per 600 sec per access token.

由于我仅使用新的Graph API，我从未遇到手动传递访问令牌的需要。我相信有一个需要传递旧的REST API。这应该意味着，对于我的应用程序的每个不同的用户，我有一个不同的访问令牌，我的API限制在接下来的600秒重置。任何人都可以确认？

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?

所以作为一个整体，我的应用程序可能有一百万个用户，让我为每个用户的访问令牌做出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.

任何人都可以评论？

推荐答案

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屋！