Incorrect “API calls limit exceeded” error

Aspose.Words Cloud Product Family
1

Hello Aspose Support Team,

I run into an error message showing: “Message”: “Application API Calls per month limit exceeded. API Calls per month limit set on the application is 100.”. The issue is that i used it less than 10 times and my limit for application is set to 150. Is this possible a bug? Can you please provide me information on how to solve this problem?

Thank you

2

@stanislav.sol

Explanation of the “API Calls per month limit exceeded” error

Aspose Cloud services enforce a per‑application quota that limits the number of API calls that can be made in a calendar month. When the quota is reached, any subsequent request returns an error similar to:

{
  "Message": "Application API Calls per month limit exceeded. API Calls per month limit set on the application is 100."
}

Even if you believe you have made only a few calls, the following situations can cause the limit to be reached unexpectedly:

Possible cause Why it happens What to check
Multiple services used (e.g., Words + Storage) Each service call counts toward the same application quota. A single operation may involve several hidden calls (upload → convert → download). Review the request flow in your code; count how many HTTP calls are issued per logical operation.
Background or retry logic Automatic retries on failure or background jobs can silently generate extra calls. Ensure you are not re‑triggering the same request in a loop or via a scheduled task.
Wrong Application ID/Key Calls made with a different app’s credentials will be charged to that app’s quota. Verify that the App SID and App Key used in every request belong to the application that has the 150‑call limit.
Shared usage across team members All developers using the same app credentials share the same quota. Confirm that no other team members are consuming the quota under the same credentials.
Previous month’s leftover Some accounts may have a rolling 30‑day window rather than a strict calendar month. Check the exact reset date in the Aspose Cloud Dashboard.

How to resolve the issue

  1. Check your current usage

    • Log in to the Aspose Cloud Dashboard.
    • Open “Applications” → Your Application → Usage.
    • Verify the API Calls count and the date of the next reset.

  2. Identify excessive calls

    • Enable request logging in your code (e.g., using a proxy like Fiddler or logging middleware) to see the exact number of HTTP requests per operation.
    • Look for patterns such as:
      // Example: three calls for a single conversion
storage.UploadFile(...);   // 1 call
wordsApi.ConvertDocument(...); // 1 call
storage.DownloadFile(...); // 1 call
    • Consolidate where possible (e.g., keep the file in storage and reuse the same URL for multiple conversions).

  3. Correct the credentials

    // Ensure you use the App SID/Key of the 150‑call app
var config = new Aspose.Words.Cloud.Sdk.Configuration
{
    ClientId = "<YourAppSID>",
    ClientSecret = "<YourAppKey>"
};
var wordsApi = new Aspose.Words.Cloud.Sdk.WordsApi(config);
    • Double‑check that no hard‑coded test credentials are accidentally deployed.

  4. Request a quota increase (if the 150‑call limit is insufficient)

    • Open a ticket through the Aspose Cloud Support Portal or reply to this thread with the following details:
      • Application name / ID
      • Desired monthly limit
      • Approximate expected call volume per month
    • Our support team will raise the limit for you (usually within 24 h).

  5. Implement a safeguard (optional)

    • Add logic to monitor remaining calls and pause or throttle operations before the limit is hit:
      var usage = await new Aspose.Storage.Cloud.Sdk.StorageApi(config)
                  .GetApplicationUsageAsync();
if (usage.ApiCallsRemaining < 10)
{
    // Notify admin or switch to a fallback mode
}

Quick checklist

  • [ ] Verify the App SID / App Key used in all requests.
  • [ ] Check the Dashboard for actual usage and reset date.
  • [ ] Review code for multiple hidden calls per logical operation.
  • [ ] Ensure no other team member or background job is consuming the quota.
  • [ ] If needed, request a higher quota via support.

If after performing these steps the usage still does not match what you see in the dashboard, please provide:

  • Your Application ID (App SID) (do not share the secret).
  • A short snippet showing how you initialize the Aspose Cloud SDK.
  • The date range during which the error occurs.

With that information we can investigate further and confirm whether a system bug is involved.

Helpful links

Feel free to reply with the requested details, and we’ll be happy to assist you further.

3

Please share your client id, I will send it to the billing team and they will check why this happens

4

Hi, here is my client id: 706f00a4-43bc-4192-b8e0-fc9bd22eec31

5

Thanks for sharing the client ID. I shared it with the billing team, and I am now waiting for their response.
upd. They told me this issue is fixed and will be deployed soon.

1 Like
6

I still cannot use the service. It’s only showing that number was increased to 150, but no conversion yet

7

Till now i only received the token from the API, but i didn’t managed to do any needed conversion docx to html. We are in hurry, because we need to complete PoC with your application until end of the next week. In case this problem will not be solved quickly we will need to find another application. Below is log we are receiving from your API:

*** Script: Aspose convert failed: 403 {
“Error”: {
“Code”: “accessRestricted”,
“Message”: “Application API Calls per month limit exceeded. API Calls per month limit set on the application is 150.”,
“Description”: “Operation Failed. A limit was hit.”
}
}: no thrown error

8

The fix will be available later today.

9

Hello, the problem is still the same

10

I asked them to resolve it ASAP. When I get the answer I will notify you.

11

I’ve been told that they deployed fix, so please try, if issue is still there, they will delete some cached values for your client id.

12

Can you please ask them to clear the cache?

13

They told me that it didn’t help, it’s a bit weird as this error exists on your account right after the registration, so they will try to create a new one, for testing, if it wouldn’t make it clear why this happens, they will use your account to replicate the issue(just a couple of requests).

1 Like
14

Could you please create another account to check if it works on your side, as they couldn’t find the root cause of the issue?

15

Hello, i already created another account, but the problem remains the same. Might be some issue with new created accounts… or i am just unlucky

16

Please share a new client id as well to test, as we need as much information as possible to resolve it asap. We already tried creating new accounts from different countries and it works fine, so we need to understand how your process is different from ours