DEV Community: Nilanjan Kamila

How to Standardize API Responses in Laravel (Clean JSON Response Structure)

Nilanjan Kamila — Mon, 01 Jun 2026 09:57:28 +0000

When building APIs in Laravel, one common problem developers face is inconsistent JSON responses.

Different controllers often return different response formats:

{
  "status": true,
  "data": {}
}

Another endpoint might return:

{
  "success": true,
  "user": {}
}

And another:

{
  "message": "Created successfully"
}

As APIs grow, this inconsistency makes frontend integration, debugging, and maintenance much harder.

To solve this problem, I built API Response Formatter, a Laravel package that helps standardize API responses across your entire application.

Resources

📦 Packagist

https://packagist.org/packages/nilanjan-k/api-response-formatter

⭐ GitHub Repository

https://github.com/nilanjan-k/api-response-formatter

👨‍💻 My GitHub Profile

https://github.com/nilanjan-k

If you find the package useful, consider giving it a star on GitHub.

Why Standardized API Responses Matter

Consistent API responses provide several benefits:

Better Frontend Integration

Frontend applications always know what response structure to expect.

Easier Error Handling

Clients can process success and error responses consistently.

Improved Maintainability

Developers don't need to remember different response formats across endpoints.

Better Developer Experience

API consumers can work with predictable response structures.

The Problem

Without a response formatter:

User Endpoint

{
  "success": true,
  "user": {
    "id": 1,
    "name": "John"
  }
}

Product Endpoint

{
  "status": true,
  "data": {
    "id": 5,
    "name": "Laptop"
  }
}

Order Endpoint

{
  "message": "Order created successfully"
}

The API becomes inconsistent.

Introducing API Response Formatter

API Response Formatter provides a clean and standardized JSON response structure for Laravel applications.

Features

✅ Consistent API responses

✅ Laravel integration

✅ Success responses

✅ Error responses

✅ Clean JSON formatting

✅ Lightweight and simple

✅ Developer-friendly

Installation

Install via Composer:

composer require nilanjan-k/api-response-formatter

Example Usage

Success Response

return ApiResponse::success(
    $user,
    'User fetched successfully'
);

Output:

{
  "success": true,
  "message": "User fetched successfully",
  "data": {
    "id": 1,
    "name": "John"
  }
}

Error Response

return ApiResponse::error(
    'User not found',
    404
);

Output:

{
  "success": false,
  "message": "User not found",
  "code": 404
}

Benefits for Large Applications

As your Laravel application grows:

More controllers
More endpoints
More developers

A standardized response format becomes increasingly important.

API Response Formatter helps enforce consistency across your project.

Who Should Use This Package?

This package is useful for:

Laravel REST APIs
SaaS applications
Mobile app backends
Vue.js APIs
React APIs
Next.js backends
Enterprise Laravel applications
Microservices

Why I Built This Package

While working on Laravel APIs, I noticed that response formatting was often duplicated across projects.

Every project ended up creating custom helper functions or response structures.

I wanted a simple package that developers could install and immediately start using to keep their APIs clean and consistent.

That's why I created API Response Formatter.

Future Improvements

Potential future enhancements include:

Pagination support
Resource integration
Response macros
API versioning support
Localization support
Custom response templates

Contributions and suggestions are welcome.

Contributing

GitHub Repository:

https://github.com/nilanjan-k/api-response-formatter

Feel free to open issues, submit pull requests, or suggest new features.

About Me

I'm Nilanjan, a PHP and Laravel developer passionate about building open-source tools and packages that improve developer productivity.

GitHub:

https://github.com/nilanjan-k

Support the Project

⭐ Star the repository

https://github.com/nilanjan-k/api-response-formatter

📦 Install via Packagist

https://packagist.org/packages/nilanjan-k/api-response-formatter

🐛 Found a bug or have an idea?

Open an issue on GitHub.

Conclusion

A consistent API response structure improves maintainability, frontend integration, debugging, and overall developer experience.

Instead of manually formatting responses throughout your Laravel application, API Response Formatter helps you standardize everything with a simple and reusable approach.

How do you currently handle API responses in Laravel?

I'd love to hear your approach in the comments.

How to Block Disposable Email Addresses in Laravel (Prevent Fake Registrations)

Nilanjan Kamila — Mon, 01 Jun 2026 09:00:12 +0000

If your Laravel application allows user registration, there's a good chance you've encountered disposable email addresses.

These temporary email services allow users to create email accounts that expire after a short period of time. While they can be useful for privacy-conscious users, they are frequently used to:

Create fake accounts
Abuse free trials
Bypass verification systems
Exploit referral programs
Generate spam registrations

For SaaS products, communities, e-commerce platforms, and membership websites, disposable emails can become a serious problem.

To solve this issue, I built TempMailBlocker, an open-source Laravel package that helps developers detect and block temporary email addresses during validation.

Resources

📦 Packagist

https://packagist.org/packages/nilanjan-k/tempmailblocker

⭐ GitHub Repository

https://github.com/nilanjan-k/tempmailblocker

👨‍💻 My GitHub Profile

https://github.com/nilanjan-k

If you find this package useful, consider giving it a star on GitHub.

Why Block Disposable Emails?

Disposable email providers offer temporary inboxes that users can create instantly without registration.

Common examples include:

Temp Mail
Mailinator
Guerrilla Mail
10 Minute Mail

Although these services have legitimate uses, they are often abused.

Problems Caused by Disposable Emails

Fake User Registrations

Users can create multiple accounts using temporary addresses.

Free Trial Abuse

A single user can repeatedly sign up for free trials.

Referral Fraud

Reward systems become vulnerable to exploitation.

Poor Email Deliverability

Disposable addresses can negatively affect email engagement metrics.

Community Spam

Forums and communities often experience increased spam registrations.

Introducing TempMailBlocker

TempMailBlocker is a Laravel package that detects and blocks disposable, temporary, and throwaway email addresses during validation.

Features

✅ Laravel validation integration

✅ Disposable email detection

✅ Lightweight and fast

✅ Open source

✅ Easy Composer installation

✅ Simple implementation

Installation

Install the package via Composer:

composer require nilanjan-k/tempmailblocker

Quick Start

Use the validation rule in your Laravel application:

use Illuminate\Support\Facades\Validator;

Validator::make($request->all(), [
    'email' => [
        'required',
        'email',
        'not_temp_email'
    ]
]);

That's it.

The package will automatically detect and reject disposable email domains.

Example

Valid Email Addresses

john@gmail.com

sarah@outlook.com

developer@yahoo.com

Disposable Email Addresses

user@tempmail.com

test@mailinator.com

fake@guerrillamail.com

These addresses will be blocked during validation.

How It Works

The package extracts the domain from the submitted email address.

Example:

user@tempmail.com

Extracted domain:

tempmail.com

The domain is then checked against a maintained list of disposable email providers.

If a match is found, validation fails.

Why Use TempMailBlocker?

Feature	TempMailBlocker
Laravel Integration	✅
Validation Rule Support	✅
Composer Install	✅
Open Source	✅
Lightweight	✅
Disposable Email Detection	✅
Easy Setup	✅

Who Should Use This Package?

TempMailBlocker is useful for:

SaaS applications
Membership websites
Online communities
E-commerce platforms
Referral systems
Subscription services
Newsletter platforms
Any Laravel application with user registration

Real-World Example

Imagine you're running a SaaS platform that offers a 14-day free trial.

Without disposable email protection:

User creates account
↓
Uses free trial
↓
Creates temporary email
↓
Registers again
↓
Gets another free trial

This cycle can continue indefinitely.

Blocking disposable emails helps reduce this abuse and improves the quality of user registrations.

Why I Built This Package

While working on Laravel projects, I repeatedly needed a simple way to block temporary email providers.

Most solutions either required custom implementations or external services.

I wanted something that developers could install quickly and integrate directly into Laravel validation.

That's why I created TempMailBlocker.

Future Improvements

Some ideas for future releases include:

Expanded disposable domain database
Configurable allowlists
Configurable blocklists
Automatic domain updates
Performance enhancements
Additional validation options

Suggestions and contributions are always welcome.

Contributing

Contributions, feature requests, and bug reports are welcome.

GitHub Repository:

https://github.com/nilanjan-k/tempmailblocker

Feel free to open an issue or submit a pull request.

About Me

I'm Nilanjan, a PHP and Laravel developer who enjoys building open-source tools and packages that help developers solve real-world problems.

You can find more of my work here:

https://github.com/nilanjan-k

Support the Project

If TempMailBlocker helps secure your Laravel applications:

⭐ Star the repository

https://github.com/nilanjan-k/tempmailblocker

📦 Install via Packagist

https://packagist.org/packages/nilanjan-k/tempmailblocker

🐛 Found a bug or have an idea?

Open an issue on GitHub.

Conclusion

Disposable email addresses can negatively impact user quality, referral systems, free trials, and overall platform security.

By integrating disposable email detection into your Laravel validation workflow, you can significantly reduce fake registrations and improve the quality of your user base.

If you'd like to try it out, check out TempMailBlocker on GitHub and Packagist.

Have you dealt with disposable email abuse in your Laravel applications?

I'd love to hear your experiences and solutions in the comments.