You need to enable JavaScript to run this app.
优惠活动
大模型
产品
解决方案
定价
更多

FB Rate Limit Error 613咨询:限流基于账号ID还是endpoint?

Understanding Facebook Graph API Error #613: Endpoint vs. Account-Based Throttling

Let's break this down clearly based on the error message and your API request:

Key Conclusion

This rate limit is triggered specifically for the delivery_estimate endpoint (referred to as the "outcome prediction api" in the error message), and it's tracked against the combination of your app (via the access token) and the target ad account (act_xxx).

Why This Is the Case

Look at the error details you shared:

{"error":{"message":"(#613) Calls to outcome prediction api have exceeded the rate of 4500 calls per 60 seconds.", "type":"OAuthException", "code":613,"fbtrace_id":"A5DNtRrGa7+"}}

The error explicitly calls out "calls to outcome prediction api" — this is Facebook's internal name for the delivery_estimate endpoint you're hitting with your request:

https://graph.facebook.com/v2.11/act_xxx/delivery_estimate?access_token=xxx

Facebook's Graph API applies granular rate limits per endpoint, not just a global account-wide cap. For this specific endpoint, the threshold is 4500 requests per 60 seconds, counted against the pair of your authenticated app (from the access token) and the target ad account (act_xxx).

Quick Recap

  • The limit is tied directly to the delivery_estimate endpoint (not a broad account-level cap)
  • The count tracks how many times your app calls this endpoint for the specific act_xxx ad account
  • You'll need to throttle your requests to this endpoint to stay under the 4500/60s threshold

内容的提问来源于stack exchange,提问作者Tianbing Leng

相关产品推荐
方舟 Agent Plan

超全模态模型 × Harness 升级,最新支持 Deepseek-V4.1-Flash、GLM-5.3 系列、Doubao-Seedream-5.0-pro、Kimi-K3 (部分), 限时 9.9 元起

最近更新时间:2026.05.21 07:14:48