How to Increase WooCommerce API Limits in 2026 for UK Stores
16 August 2026
Learn how to increase WooCommerce API limits in 2026 for faster UK online stores. Step-by-step fixes for pagination, server limits, and performance.
Understanding WooCommerce API Limits
WooCommerce's REST API is designed to handle large data exchanges, but it ships with conservative limits to protect server resources. By default, the API returns only 10 items per request, with an absolute maximum of 100 per_page. However, the real bottleneck for UK store owners often lies in server configuration rather than the API itself. PHP memory limits, execution timeouts, and hosting plan restrictions can all interfere with high-volume requests. Knowing these layers helps you diagnose exactly where your limits are being hit. Start by testing a simple request with per_page=100 to see what your current server will allow, then work through the adjustments below.
Stop Truncated Data: Adjusting per_page and Pagination
The quickest win is to explicitly set per_page to a higher value in your API requests. For instance, adding ?per_page=100 to a products endpoint will return up to 100 items, far more than the default 10. But don't simply assume the response contains everything. Use the Link header in the response to check for additional pages, and loop through them with page numbers. This approach is essential for synchronising large UK product catalogs or migrating data between systems. Always handle pagination gracefully in your code to ensure you capture every record without overloading the server or risking timeouts.
Server-Level Limits: PHP Memory, Execution Time, and Max Input Vars
Many UK hosts, especially shared providers, set conservative PHP values that throttle API performance. The critical settings are memory_limit, max_execution_time, and max_input_vars. For a typical WooCommerce API call, you'll want at least 256MB of PHP memory and 120 seconds of execution time. If you're on a managed UK host like Krystal or 34SP, you can often adjust these via the control panel or a local php.ini file. For unmanaged VPS or dedicated servers, edit your PHP-FPM pool configuration. Monitoring your server's error logs will reveal if these limits are being hit during API requests.
Fixing WooCommerce API Timeouts for Large UK Catalogs
Timeouts are a common frustration when dealing with API requests that involve thousands of products. They occur when server resources are exhausted before the response is generated. To fix this, optimise the backend by enabling caching for object and term queries, and consider using a plugin like WP Rocket or W3 Total Cache to reduce server load. You can also increase timeout values in your API client, but the server's own limits must be raised as well. For particularly heavy tasks, schedule cron jobs or use a queue system like WP-CLI to process data in chunks, rather than relying on a single, massive API request.
Advanced Tactics: Custom Endpoints and Plugins for Higher Limits
When the standard API just isn't enough, UK developers often create custom REST endpoints using the register_rest_route function. This gives you full control over query parameters and limits, allowing you to bypass WooCommerce's built-in caps. Alternatively, plugins like 'WooCommerce API Advanced' or 'WP REST API Controller' can expand per_page limits and improve performance. Before installing any plugin, verify it's compatible with your WordPress version and adheres to WooCommerce standards. Also remember to consider GDPR implications when handling customer data via APIs – ensure your custom endpoints only expose necessary information and use appropriate authentication methods.
FAQ
By default, the WooCommerce REST API returns a maximum of 10 items per request. You can override this using the per_page parameter, but the server hard-caps at 100. This ensures that requests don't overwhelm shared hosting environments typically used by smaller UK stores.