Question: I have a bot from Bot Libre connected to my Facebook page and Facebook Messenger.
The bot has its own Facebook app, that has been approved, and has been running for several month without issues.

But the last two days I suddenly get the error below any time I call a Facebook API,

```
message - (#32) Page request limited reached
code - 32
Relevant information for error recovery can be found on the Facebook Developers Document:
    https://developers.facebook.com/docs/graph-api/using-graph-api/#errors

```

I tried refreshing the bot page access token, but still get the same error?

When I look at the app, it only shows 14 API calls today... don't see how I can be hitting a limit. How do you see the API calls/day for a Facebook page access token?

Anyone else have this issue or know anything about it?

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

What's my current rate limit?
=============================

---

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

Engagement includes **a click on the Page or Page content**.

**NOTE**: You can get this value with the [Insights API](https://developers.facebook.com/docs/graph-api/reference/v2.6/insights) **page\_engaged\_users** metric.

What's my current rate?
=======================

---

Your **current rate** is calculated by using:

* **Call count**
* **Total time used**
* **CPU time used**

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

```

What's my current "Call count" limit?
=====================================

---

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

What can I do?
==============

---

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}

```
3. If you still need a higher rate limit, consider **requesting a rate limit increase**.

	* Go to your App (not Page) dashboard:

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

	```
	* Scroll down to the last block called "API limit at page level".
	* Select you page in the combobox.
	* Click on the "API Limit Increase Request" button. You'll be requested to fill a form including the reason for your app to reach the rate limit and why your app needs a higher rate limit.

Detailed information
====================

---

For more information, please see:

* [Improving Rate Limits for Page Management Apps](https://developers.facebook.com/blog/post/2016/06/16/page-level-rate-limits/) developers announcement.
* [API Graph Rate Limiting](https://developers.facebook.com/docs/graph-api/advanced/rate-limiting) advanced documentation.
I just faced similar problem with new desktop app, please look at [this](https://developers.facebook.com/blog/post/2016/06/16/page-level-rate-limits/). Also look at your app Page Level Rate Limiting regarding your page (select it in combobox).