Express Route Methods

HTTP Methods as Express Functions

Express mirrors HTTP verbs directly as methods on app (and on express.Router() instances): app.get(), app.post(), app.put(), app.patch(), app.delete(), plus app.all() for matching any method.

Following REST conventions, each verb implies an intent, GET reads, POST creates, PUT/PATCH update, DELETE removes, which keeps your API predictable for anyone consuming it.

app.get('/users', listUsers);       // read
app.post('/users', createUser);     // create
app.put('/users/:id', replaceUser); // full update
app.patch('/users/:id', updateUser);// partial update
app.delete('/users/:id', removeUser);// delete

Each line targets the same or a related path, but a different method, giving you a full CRUD surface for the /users resource.

app.route() for Grouped Methods

app.route('/users/:id')
  .get(getUser)
  .put(replaceUser)
  .patch(updateUser)
  .delete(removeUser);

• app.route(path) returns a chainable object for registering multiple methods on one path.
• It avoids repeating the same path string across several separate calls.
• Works the same way on an express.Router() instance as it does on app.
• app.all(path, fn) runs for every HTTP method on that path.

HTTP Method Cheatsheet

Conventional meaning of each method Express supports, and when to use it.

PUT vs PATCH

PUT conventionally replaces the entire resource, the client is expected to send a complete representation. PATCH updates only the fields provided, leaving the rest of the resource untouched. Many real APIs are lenient about this distinction, but sticking to it makes your API's behavior predictable.

app.put('/users/:id', (req, res) => {
  // expects the full user object
  users[req.params.id] = req.body;
  res.json(users[req.params.id]);
});

app.patch('/users/:id', (req, res) => {
  // merges only provided fields
  users[req.params.id] = { ...users[req.params.id], ...req.body };
  res.json(users[req.params.id]);
});

Using app.all()

app.all() is useful for logic that should run regardless of method, maintenance mode checks, method-agnostic logging, or a catch-all for a deprecated endpoint that should return the same error no matter how it's called.

app.all('/legacy-endpoint', (req, res) => {
  res.status(410).json({ error: 'This endpoint has been removed' });
});

Common Mistakes

• Using GET requests to trigger data changes, breaking caching and REST expectations.
• Treating PUT and PATCH as fully interchangeable across a whole API without documenting the choice.
• Forgetting that app.all() matches every method, including ones you didn't intend to support.
• Repeating the same path string across five separate app.METHOD() calls instead of using app.route().

Key Takeaways

• Express provides a method per HTTP verb: get, post, put, patch, delete, and more.
• REST conventions map GET to reads, POST to creates, PUT/PATCH to updates, DELETE to removals.
• app.route(path) groups multiple methods for the same path into one chain.
• app.all() matches a path for every HTTP method.