Facebook api:(#4)达到申请请求限制 [英] Facebook api: (#4) Application request limit reached

查看:388
本文介绍了Facebook api:(#4)达到申请请求限制的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

自11月下旬以来,我们在Facebook API上达到了应用限制。
我们正在获取用户的照片,并选择了25个朋友的照片→这是在用户签名(我们正在为用户构建相册)时完成的。

Since late November we are hitting the application limit on the Facebook API. We are fetching user's photos, and selected 25 friends photos → this is done when a user signatures in (we are building albums for the users).

以上行动有限,但不限于11月底。
我们正在使用批量调用从相册中获取照片 -
有没有更好的方式来获取此信息而不受限制?

The above action is limited, but it was not limited till end of November. We are using batch calls to get photos from albums - is there a better way to get this info without being limited?

BTW,根据到Facebook我们每天正在做1M的电话,但是根据我们的计数,我们每天正在做180K电话。

BTW, according to Facebook we are doing 1M calls per day, but according to our count we are doing 180K calls per day.

只有用户的照片没有他朋友的照片不是

Fetching only the user's photos without his friend's photos is not a solution for us.

推荐答案

Facebook API限制没有真正记录,但显然是这样的: 600次/ 600秒,每个令牌&每IP 。由于网站受到限制,引用相关部分:

The Facebook API limit isn't really documented, but apparently it's something like: 600 calls per 600 seconds, per token & per IP. As the site is restricted, quoting the relevant part:


经过与Facebook平台团队的一些测试和讨论,没有官方限制在文档中知道或可以找到。但是,我发现每600秒600个电话,每个令牌&每个IP都是他们阻止你的地方。我也看过一些基于应用程序的速率限制,但没有任何数字。

After some testing and discussion with the Facebook platform team, there is no official limit I'm aware of or can find in the documentation. However, I've found 600 calls per 600 seconds, per token & per IP to be about where they stop you. I've also seen some application based rate limiting but don't have any numbers.

一般来说,每秒一次呼叫不应该受限制。在表面上看来,这似乎是非常有限制的,但请记住,您可以批量某些呼叫并使用订阅API来获取更改。

As a general rule, one call per second should not get rate limited. On the surface this seems very restrictive but remember you can batch certain calls and use the subscription API to get changes.

正如您可以访问通过JavaScript SDK在客户端的Graph API;我想如果您从客户端发送照片请求,您将不会按照任何应用程序限制,因为用户(每个具有唯一ID)都是获取数据,而不是您的应用服务器(唯一ID)。

As you can access the Graph API on the client side via the Javascript SDK; I think if you travel your request for photos from the client, you won't hit any application limit as it's the user (each one with unique id) who's fetching data, not your application server (unique ID).

如果您通过一个服务器完成所有操作,这可能意味着一个巨大的重构。但是如果您有这么多请求(因为它会给您的服务器一个呼吸),似乎是最好的解决方案。

This may mean a huge refactor if everything you do go through a server. But it seems like the best solution if you have so many request (as it'll give a breath to your server).

否则,您可以尝试 批次请求,但我想你已经走了

Else, you can try batch request, but I guess you're already going this way if you have big traffic.

如果没有这样做,根据Facebook平台政策,您应该联系他们。

If nothing of this works, according to the Facebook Platform Policy you should contact them.


如果超过,或计划超过以下任何阈值,请与我们联系,因为您可能需要额外条款:(> 5M MAU)或(每天> 100M API来电)或(>每天> 500万次展示次数)。

If you exceed, or plan to exceed, any of the following thresholds please contact us as you may be subject to additional terms: (>5M MAU) or (>100M API calls per day) or (>50M impressions per day).

这篇关于Facebook api:(#4)达到申请请求限制的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆