Facebook(#32)页面请求已达到限制 [英] Facebook (#32) Page request limited reached

问题描述

尝试使用Facebook Graph API访问页面时出现以下错误.

I am getting the following error while I am trying to access my page using Facebook Graph API.

{
error: {
message: "(#32) Page request limited reached",
type: "OAuthException", 
code: 32,
fbtrace_id: "F6d20m1iihx"

} }

在Facebook API文档中找不到任何内容.这与我的API或页面有关吗?

Could not find anything in Facebook API Documentation. Is this related to my API or page?

推荐答案

它与您的信息页有关.达到应用程序限制消息错误，代码错误4.

It is related to your Page. An App limit reached message error would have the code error 4.

自2016年7月11日以来，Facebook已改善"了页面的Facebook Graph API速率限制 .

Since July 11, 2016 Facebook has "improved" the Facebook Graph API rate limit for page.

现在，您的当前费率限制(当前24小时窗口)是根据最近24小时窗口的参与用户数计算的.

Now your current rate limit (current 24-hour window) is calculated using last 24-hour window number of engaged users.

参与包括点击页面或页面内容.

注意:您可以通过 Insights API page_engaged_users 指标.

NOTE: You can get this value with the Insights API page_engaged_users metric.

您的当前汇率是通过使用以下方式计算的:

Your current rate is calculated by using:

• 通话次数
• 已用总时间
• 已使用的CPU时间

• Call count
• Total time used
• CPU time used

您可以在页面> 见解> API 部分中查看当前汇率与当前汇率限制:

You can check you current rate compared to your current rate limit on your page > Insights > API section:

https://www.facebook.com/<your-page-name>/insights/?section=navAPI

我当前的通话次数"限制是多少?

---

您可以在24小时内为每个参与的用户拨打4800个电话.

What's my current "Call count" limit?

---

You can make 4800 calls for each engaged user during a 24-hour period.

1. 等待吸引更多粉丝，以便获得更高的费率限制.

2. 每个Facebook Graph API响应都包含一个 X-Page-Usage 标头，其中包含 call_count ， total_cputime 和 total_time 百分比值(如果Page的使用率实际上是0％，则没有标题).当这些指标中的任何一个超过100时，管理该页面的应用将受到速率限制. 使用该值评估您的API使用情况，这样您就可以平衡它，而不会被阻止.页面利用率标头示例:

1. Wait to get more fans to be able to get a higher rate limit.

2. Each Facebook Graph API response includes a X-Page-Usage header with call_count, total_cputime and total_time percentage values (There is no header if the Page's utilization is effectively 0%). When any of these metrics exceed 100, the app managing that page will be rate limited. Use that values to evaluate your API usage so you can balance it and never get blocked. Example of page utilization header:

X-Page-Usage : {'call_count' : 85, 'total_cputime' : 56, 'total_time' : 60}

如果您仍然需要更高的速率限制，请考虑请求提高速率限制.

• 转到您的应用程序(非页面)"仪表板:

• Go to your App (not Page) dashboard:

https://developers.facebook.com/apps/<your-api-ID>/dashboard/

向下滚动到最后一个块，称为页面级别的API限制".

Scroll down to the last block called "API limit at page level".

详细信息

---

有关更多信息，请参见:

Detailed information

---

For more information, please see:

• 提高页面管理应用程序的速率限制开发人员公告.
• API图速率限制高级文档.
>

• Improving Rate Limits for Page Management Apps developers announcement.
• API Graph Rate Limiting advanced documentation.

这篇关于Facebook(#32)页面请求已达到限制的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！