Laravel `findOrFail()` vs. `first()` for API Responses

Table Of Contents

• The Problem: Which Method for API Endpoints?
• When to Use Which Method

The Problem: Which Method for API Endpoints?

When building APIs, should you use findOrFail() that throws exceptions or first() that returns null? The answer depends on your error handling strategy:

// Using findOrFail() - throws ModelNotFoundException automatically
public function show($id)
{
    $user = User::findOrFail($id); // Throws 404 if not found
    return response()->json($user);
}

// Using first() - returns null, requires manual handling
public function show($id)
{
    $user = User::where('id', $id)->first();
    
    if (!$user) {
        return response()->json(['error' => 'User not found'], 404);
    }
    
    return response()->json($user);
}

// Alternative: find() with null check
public function show($id)
{
    $user = User::find($id);
    
    if (!$user) {
        return response()->json([
            'message' => 'User not found',
            'error_code' => 'USER_NOT_FOUND'
        ], 404);
    }
    
    return response()->json($user);
}

When to Use Which Method

Use findOrFail() when:

• You want Laravel's default exception handling
• Building simple CRUD APIs
• You're okay with Laravel's standard error format

Use first() or find() when:

• You need custom error messages
• Building APIs with specific error formats
• You want to handle multiple conditions

// findOrFail() with custom exception handling
public function show($id)
{
    try {
        $user = User::findOrFail($id);
        return response()->json(['data' => $user]);
    } catch (ModelNotFoundException $e) {
        return response()->json([
            'error' => 'Resource not found',
            'message' => "User with ID {$id} does not exist",
            'code' => 'RESOURCE_NOT_FOUND'
        ], 404);
    }
}

// first() with additional business logic
public function show($id)
{
    $user = User::where('id', $id)
               ->where('active', true) // Additional condition
               ->first();
    
    if (!$user) {
        // Could be inactive or non-existent
        $exists = User::where('id', $id)->exists();
        
        return response()->json([
            'error' => $exists ? 'User is inactive' : 'User not found',
            'code' => $exists ? 'USER_INACTIVE' : 'USER_NOT_FOUND'
        ], $exists ? 403 : 404);
    }
    
    return response()->json(['data' => $user]);
}

// Performance consideration: exists() vs count()
$userExists = User::where('email', $email)->exists(); // Better
$userCount = User::where('email', $email)->count();   // Slower for existence checks

The findOrFail() method is ideal for simple APIs where Laravel's default "No query results for model" error message is acceptable. Use first() when you need custom error responses, additional query conditions, or want to avoid exceptions in your controller logic.

Related: Laravel Collections: Beyond Basic Array Operations | Laravel Events and Listeners: Building Decoupled Applications | Laravel API Development: Best Practices and Security | Advanced Eloquent Techniques and Optimizations in Laravel | Error Handling & Exception Management 2025: Complete Guide