API resource controllers in Laravel - Step-by-Step Execution

Concept Flow - API resource controllers

Client sends HTTP request

↓

Route matches resource controller method

↓

Controller method executes

↓

index

↓

Fetch data

↓

Return JSON response to client

The flow shows how HTTP requests map to controller methods that handle data and return JSON responses.

Execution Sample

Laravel

Route::apiResource('books', BookController::class);

// BookController methods:
public function index() { return Book::all(); }
public function show($id) { return Book::findOrFail($id); }

Defines API routes for books and shows how index and show methods return data.

Execution Table

Step	HTTP Request	Route Matched	Controller Method	Action	Response
1	GET /books	books.index	index()	Fetch all books	JSON list of all books
2	GET /books/3	books.show	show(3)	Fetch book with ID 3	JSON data of book 3
3	POST /books	books.store	store()	Validate & save new book	JSON data of created book
4	PUT /books/3	books.update	update(3)	Validate & update book 3	JSON data of updated book
5	DELETE /books/3	books.destroy	destroy(3)	Delete book 3	204 No Content response
6	GET /books/999	books.show	show(999)	Book 999 not found	404 Not Found error

💡 Execution stops after sending JSON response or error to client.

Variable Tracker

Variable	Start	After Step 1	After Step 2	After Step 3	After Step 4	After Step 5	After Step 6
books	empty	[book1, book2, book3]	[book1, book2, book3]	[book1, book2, book3, newBook]	[book1, book2, updatedBook, newBook]	[book1, book2, newBook]	[book1, book2, newBook]
bookId	null	null	3	null	3	3	999
response	null	JSON list	JSON book 3	JSON new book	JSON updated book	204 No Content	404 Not Found

Key Moments - 3 Insights

Why does the show method return a 404 error for a missing ID?

Because findOrFail throws an error if the book is not found, as shown in step 6 of the execution_table.

How does Laravel know which controller method to call for each HTTP request?

The apiResource route maps HTTP verbs and URLs to controller methods automatically, as seen in the Route Matched column.

What response does the destroy method send after deleting a record?

It sends a 204 No Content response, indicating success without returning data, shown in step 5.

Visual Quiz - 3 Questions

Look at the execution_table, what response does the index method return at step 1?

A JSON list of all books

B JSON data of book 3

C 204 No Content response

D 404 Not Found error

💡 Hint

Check the Response column at step 1 in the execution_table.

At which step does the controller return a 404 error?

A Step 2

B Step 6

C Step 4

D Step 5

💡 Hint

Look for 404 Not Found in the Response column of the execution_table.

If a new book is added, how does the 'books' variable change after step 3?

A It stays the same

B It removes a book

C It adds the new book to the list

D It becomes empty

💡 Hint

Check the variable_tracker row for 'books' after step 3.

Concept Snapshot

API resource controllers map HTTP verbs and URLs to controller methods.
Common methods: index, show, store, update, destroy.
They handle data fetching, validation, saving, updating, and deleting.
Responses are JSON or HTTP status codes.
Routes are defined with Route::apiResource.
Missing records return 404 errors automatically.

Full Transcript

API resource controllers in Laravel connect HTTP requests to controller methods automatically using Route::apiResource. When a client sends a request like GET /books, Laravel calls the index method to fetch all books and returns them as JSON. For GET /books/3, it calls show(3) to fetch one book or returns a 404 error if not found. POST requests call store to validate and save new data. PUT requests call update to modify existing data. DELETE requests call destroy to remove data and respond with 204 No Content. The execution table shows each step's request, matched route, controller method, action, and response. The variable tracker shows how data changes after each step. Key moments clarify why 404 errors happen, how routes map to methods, and what responses are sent after deletion. The visual quiz tests understanding of responses, error steps, and data changes. This helps beginners see how Laravel API resource controllers handle requests and responses step-by-step.