If you see an error similar to:

Daily API Requests limit for 'example.com' domain has been reached.

this means that your website has reached the maximum number of API data requests available for the current daily period.

This does not necessarily mean that normal website visitors are generating too many requests. AllForJoomla extensions use cached data whenever possible, so an already configured widget can normally continue working with relatively few fresh API requests.

Important: The daily limit is much more likely to be reached while creating or configuring widgets, especially when changing settings that require a different set of data from the API.

Why Does This Error Appear?

API-based AllForJoomla extensions retrieve external data such as reviews, business information, company profiles, social content, or other information required by the widget.

To avoid requesting the same information every time somebody opens your website, retrieved data is cached and reused whenever possible.

However, a new API request may be required when:

  • cached data needs to be updated;
  • a different business, company, account, profile, or other source is selected;
  • a new widget is created;
  • widget settings are changed in a way that requires another data set;
  • sorting options are changed;
  • filters are changed;
  • the number or type of requested items is changed.

Once the daily API request limit for the domain has been reached, operations that require additional fresh data may return the limit error.

Why Can a Widget Work for a Long Time and Then Suddenly Show This Error?

This is one of the most common situations in which the error appears.

An existing widget may work normally for days or weeks using the same configuration and cached data. During normal operation, the widget often does not need to request a completely different data set from the API.

The situation can change when you start editing the widget or create a new one.

For example, while configuring a reviews widget you may try:

  • a different business;
  • a different review sorting order;
  • a different number of reviews;
  • different review filters;
  • different rating filters;
  • another data source;
  • a new widget with different settings.

Some of these changes require the extension to request a different set of data from the API.

As a result, a short widget configuration session can sometimes generate significantly more API requests than the widget generates during normal day-to-day operation.

Example

Suppose you already have a widget displaying reviews for the same business and it has been working normally for several weeks.

You then open the Visual Builder and test several configurations:

Business A → Business B → Business C

Then you change the review order:

Newest reviews → Highest rated → Lowest rated

And then change the requested content:

10 reviews → 20 reviews → filtered reviews

Each configuration may require information that is not available in the existing cache.

This means that a few minutes of testing different widget configurations can sometimes generate more API activity than several days of normal widget operation.

Does Every Website Visitor Generate an API Request?

No.

Normal frontend page views generally use data that has already been retrieved and cached.

The API request limit is therefore not the same as the number of website visitors or widget impressions.

A website can receive many page views while generating relatively few fresh API requests.

Additional API requests are mainly needed when the extension has to retrieve or refresh data that is not already available in the cache.

Which Widget Settings Can Generate Additional API Requests?

The exact settings depend on the extension, but options that change which data must be retrieved are the most likely to generate additional API requests.

Changing the data source

For example, selecting another:

  • business;
  • company;
  • profile;
  • account;
  • location.

Changing the requested content

Depending on the extension, this may include:

  • number of reviews or other items;
  • review sorting;
  • review filters;
  • rating filters;
  • content type;
  • other parameters that change the returned data set.

These settings are different from purely visual options because the extension may need to retrieve information that has not previously been requested and cached.

Visual settings

Changes such as colors, typography, spacing, column sizes, or other purely visual settings normally do not require the same kind of external data request because they do not change the underlying data set.

What Should I Do When the Daily Limit Is Reached?

In most cases, you do not need to reinstall the extension, reconnect the widget, or recreate its configuration.

The simplest solution is to wait until API requests become available again for the next daily period.

If you are currently configuring a widget, it is a good idea to stop repeatedly changing data-related settings until the limit resets.

Otherwise, additional configuration attempts may quickly consume newly available API requests again.

Existing widgets may continue displaying previously cached data while the limit is reached, depending on the data already available in the cache.

How to Reduce API Usage While Configuring Widgets

When possible, avoid repeatedly requesting many different data combinations during a short configuration session.

  • Choose the business, company, profile, or account you intend to use before extensive customization.
  • Avoid repeatedly switching between different data sources only for testing.
  • Avoid testing every possible sorting and filtering combination in a short period.
  • Configure one widget first before creating many different variations.
  • Reuse the same data source when appropriate.
  • Avoid repeatedly refreshing or rebuilding the widget after every data-related change.
  • Make visual changes separately when possible, because these usually do not require different API data.

Is This an Extension Error?

Usually, no.

The message indicates that the daily API request allowance assigned to your website domain has been consumed.

If the widget worked normally before the message appeared, especially if the error occurred while creating a new widget or changing its data settings, the most likely cause is simply a larger-than-usual number of fresh API requests during configuration.

What If the Limit Is Reached During Normal Use?

If the error appears repeatedly even though you are not creating new widgets, changing data sources, adjusting filters, changing sorting options, or otherwise requesting different data sets, please contact AllForJoomla support.

When contacting support, please include:

  • your website domain;
  • the extension name;
  • the complete error message;
  • approximately when the error appeared;
  • whether you were editing, creating, or testing widgets before the error occurred.

This information will help us identify why the daily API request allowance is being consumed.

Summary

The “Daily API Requests limit for '...' domain has been reached” message means that the website has used its available API requests for the current daily period.

It does not necessarily indicate unusually high website traffic. In many cases, the limit is reached while creating or configuring widgets because changing a business, sorting order, number of reviews, filters, or other data-related parameters can require additional API requests.

Once the daily allowance becomes available again, widgets that require fresh data can continue retrieving it normally.