MOTOSHARE ๐Ÿš—๐Ÿ๏ธ
Turning Idle Vehicles into Shared Rides & Earnings

From Idle to Income. From Parked to Purpose.
Earn by Sharing, Ride by Renting.
Where Owners Earn, Riders Move.
Owners Earn. Riders Move. Motoshare Connects.

With Motoshare, every parked vehicle finds a purpose. Owners earn. Renters ride.
๐Ÿš€ Everyone wins.

Start Your Journey with Motoshare

Laravel Throttle Middleware: How to Increase API Rate Limit Safely and for 429 Too Many Requests

If you’re working with Laravel APIs, you might have encountered this default throttle setting:

'api' => [
    'throttle:60,1',
    'bindings',
],

This line lives in your app/Http/Kernel.php file and controls how many requests a user can make to your API. In this blog post, weโ€™ll explore what it means, why you might want to change it, and how to safely increase the rate limit for your Laravel application.


๐Ÿง  What Does 'throttle:60,1' Mean?

This throttle rule applies a rate limit to all API requests:

  • 60 = number of requests allowed
  • 1 = time in minutes

๐Ÿ” In short:

Each user (or IP) can make 60 requests per minute to your API.


๐Ÿšซ Why You Might Want to Change It

You may want to increase the throttle limit if:

  • Your frontend app sends many background requests.
  • You’re integrating with another system (like a mobile app or a microservice).
  • Users are getting 429 Too Many Requests errors frequently.

โœ… How to Increase the Throttle Value

To change the limit, go to:

app/Http/Kernel.php

Find this section:

protected $middlewareGroups = [
    'api' => [
        'throttle:60,1',
        'bindings',
    ],
];

Change it to something like:

'api' => [
    'throttle:200,1', // Allow 200 requests per minute
    'bindings',
],

Tip:

You can adjust this as needed, for example:

  • 'throttle:100,1' โ†’ 100 req/min
  • 'throttle:500,5' โ†’ 500 requests every 5 minutes

๐ŸŽฏ Apply Custom Throttle to Specific Routes (Optional)

If you donโ€™t want to increase the throttle globally, you can apply it to specific routes like this:

Route::middleware(['auth:api', 'throttle:300,1'])->get('/profile', function () {
    return response()->json(['user' => auth()->user()]);
});

Or create a group:

Route::middleware(['auth:api', 'throttle:500,5'])->group(function () {
    Route::get('/orders', 'OrderController@index');
    Route::get('/products', 'ProductController@index');
});

Bonus: Create Named Custom Throttle

In RouteServiceProvider.php:

use Illuminate\Cache\RateLimiting\Limit;
use Illuminate\Support\Facades\RateLimiter;

public function boot()
{
    RateLimiter::for('custom-api', function ($request) {
        return Limit::perMinute(300)->by($request->ip());
    });
}

Then in routes:

Route::middleware(['throttle:custom-api'])->get('/my-endpoint', 'MyController@method');

Laravel makes it easy to control your API traffic using the throttle middleware. If you’re experiencing issues like 429 Too Many Requests, just increasing the limit in Kernel.php or applying custom route-level throttling can solve your problem efficiently.

Related Posts

Step-by-Step Guide to CKA Certification Success

The world of IT has moved away from static servers. Today, everything is about speed and scale. If you work in software or infrastructure, you have likely…

Path to Google Cloud Professional DevOps Certification

In the current tech world, building an application is only half the battle. The real challenge starts when that application goes live and has to handle thousands…

Step-by-Step Guide to Implement Azure Security Technologies

In the old days of IT, we built high walls around our data centers and assumed everything inside was safe. Those days are gone. Today, the “perimeter”…

Why Practical Experience is Key in Azure DevOps Expert Training

In the fast-moving world of technology, the way we manage software has changed forever. It is no longer enough to just write code; we must now master…

Mastering Azure Storage and Data Platforms

The move to the cloud is no longer a choice for modern enterprises; it is a necessity. However, simply moving workloads to the cloud isn’t enough. Organizations…

Common Challenges in AWS Data Engineering and Solutions

As an industry veteran who has navigated the evolution from on-premise server racks to serverless cloud architectures, I have witnessed a massive shift. Companies are no longer…

0 0 votes
Article Rating
Subscribe
Notify of
guest
0 Comments
Oldest
Newest Most Voted
Inline Feedbacks
View all comments
0
Would love your thoughts, please comment.x
()
x