Why Noun-based resource naming in Rest API? - Purpose & Use Cases

The Big Idea

What if your API could speak a simple, universal language everyone understands instantly?

The Scenario

Imagine you are building a website where users can manage books, authors, and orders. You try to name your API endpoints using verbs like /getBooks, /createAuthor, or /deleteOrder. As your project grows, it becomes confusing to remember which verbs to use and how to combine them.

The Problem

Using verbs in URLs makes your API inconsistent and hard to maintain. You have to remember many different action words, and it's easy to make mistakes or misunderstand what each endpoint does. This slows down development and causes bugs.

The Solution

Noun-based resource naming uses simple, clear nouns to represent things in your system, like /books, /authors, and /orders. Actions like getting, creating, or deleting are handled by HTTP methods (GET, POST, DELETE). This makes your API easy to understand and consistent.

Before vs After

✗ Before

/getBooks
/createAuthor
/deleteOrder

✓ After

GET /books
POST /authors
DELETE /orders/{id}

What It Enables

This approach lets developers quickly understand and use your API without guessing, making teamwork and scaling much easier.

Real Life Example

Think of an online store API where you can list products with GET /products, add a new product with POST /products, or remove a product with DELETE /products/{id}. It's clear and simple for everyone.

Key Takeaways

Using nouns for resource names keeps APIs simple and consistent.

HTTP methods handle actions, so URLs stay clean and easy to remember.

This makes APIs easier to use, maintain, and scale.