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

Selenium Training: Complete Web Automation Testing Roadmap

Introduction: Problem, Context & Outcome Automated testing has become essential for modern software development. Manual testing alone is often slow, error-prone, and difficult to scale in agile…

Mastering in Scala with Spark: Complete Learning Roadmap

Introduction: Problem, Context & Outcome In today’s data-driven world, handling massive datasets efficiently is a key challenge for engineers. Traditional programming languages often struggle with performance and…

Master in PHP with Laravel: Complete Learning Roadmap

Introduction: Problem, Context & Outcome Developers often face challenges building scalable, maintainable web applications that meet modern business demands. Many struggle with outdated practices, slow development cycles,…

Master New Relic Training for DevOps Monitoring

Introduction: Problem, Context & Outcome In modern software delivery, application downtime and performance bottlenecks can have costly consequences for businesses. Developers and DevOps teams often struggle to…

Master Microservices in 2026 for DevOps Engineers

Introduction: Problem, Context & Outcome Modern engineering teams face increasing difficulty when scaling large, monolithic applications while still meeting expectations for speed, reliability, and continuous delivery. As…

Master in JavaScript with AngularJS and NodeJS for DevOps

Introduction: Problem, Context & Outcome In modern software development, many teams struggle to deliver dynamic web applications efficiently. Traditional development approaches often result in slow releases, fragmented…

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