DELETE route handling in Express - Step-by-Step Execution

Concept Flow - DELETE route handling

Client sends DELETE request

↓

Express matches DELETE route

↓

Route handler runs

↓

Perform delete operation

↓

Send response to client

↓

End

The server listens for DELETE requests, runs the handler to delete data, then sends a response back.

Execution Sample

Express

app.delete('/items/:id', (req, res) => {
  const id = req.params.id;
  deleteItemById(id);
  res.status(200).send(`Deleted item ${id}`);
});

This code deletes an item by id when a DELETE request is received at /items/:id.

Execution Table

Step	Action	Request Data	Operation	Response Sent
1	Receive DELETE /items/42	id=42	Match route '/items/:id'	No response yet
2	Extract id from req.params	id=42	id = '42'	No response yet
3	Call deleteItemById('42')	id=42	Item 42 deleted from storage	No response yet
4	Send response with status 200	id=42	No operation	Response: 'Deleted item 42'
5	End request	id=42	No operation	Response sent, connection closed

💡 Request ends after sending response confirming deletion.

Variable Tracker

Variable	Start	After Step 2	After Step 3	Final
id	undefined	'42'	'42'	'42'
response status	undefined	undefined	undefined	200
response body	undefined	undefined	undefined	'Deleted item 42'

Key Moments - 3 Insights

Why do we use req.params.id to get the id?

Because the route is defined with ':id', Express puts that part of the URL into req.params.id as shown in execution_table step 2.

What happens if deleteItemById fails or the id does not exist?

In this simple example, the code assumes success. In real apps, you should check and send error responses. Here, step 3 shows deletion assumed successful.

Why do we send a response after deleting?

HTTP requires a response to end the request. Step 4 sends status 200 and a message so the client knows the delete succeeded.

Visual Quiz - 3 Questions

Look at the execution table, what is the value of 'id' after step 2?

A '42'

B undefined

C null

D 'id'

💡 Hint

Check the 'Request Data' and 'Operation' columns at step 2 in the execution_table.

At which step is the response sent back to the client?

A Step 2

B Step 4

C Step 3

D Step 5

💡 Hint

Look at the 'Response Sent' column in the execution_table.

If the route was changed to '/items/delete/:id', which step would change in the execution flow?

A Step 3 - delete operation

B Step 4 - sending response

C Step 1 - route matching

D Step 5 - ending request

💡 Hint

Route matching depends on the URL pattern, see step 1 in execution_table.

Concept Snapshot

DELETE route handling in Express:
- Use app.delete(path, handler) to listen for DELETE requests.
- Access route params via req.params.
- Perform delete logic inside handler.
- Send response with res.status().send() to confirm.
- Always end request with a response.

Full Transcript

In Express, a DELETE route listens for HTTP DELETE requests at a specific path. When a client sends a DELETE request, Express matches the route and runs the handler function. Inside the handler, you get the id from req.params.id, perform the deletion, then send a response back with status 200 and a message confirming the deletion. The request ends after sending the response. This flow ensures the client knows the delete succeeded. Beginners often wonder why we use req.params.id, why we must send a response, and what happens if deletion fails. This example assumes success for simplicity. The key steps are receiving the request, extracting parameters, deleting the item, sending the response, and ending the request.