Understanding the 413 "Request Entity Too Large" Error

Last updated: April 4, 2025

Why am I seeing this error?

In general, the 413 "Request Entity Too Large" error occurs when a user sends a request that exceeds the allowed limit in size or complexity. This is a common error in web services and APIs, indicating that the data sent in the request is larger than the server is configured to accept.

Why do I get this error? 

If you are on Discover plan and making RPC call for dedug or trace methods, example methods: getMultipleAccounts, eth_getLogs, or eth_newFilter

In the params if you are parsing more than 5 range, this will trigger such an error. 

This range limit is a mechanism to ensure fair and efficient use of our services.  For those needing more extensive resources, upgrading to a paid plan is recommended.

What can I do to avoid this error?

To avoid this error:

  1. Stay Within the Block Range Limit: Ensure your requests do not exceed the 5 block range limit for the specified methods.

  2. Monitor Your Usage: Keep an eye on your usage to ensure you are within the rate limits of your current plan.

  3. Upgrade Your Plan: If you need a larger block range or higher rate limits, consider upgrading to a paid plan.