Course contentsShow
← System Design
Lesson 1877 of 1,91945. API Design and VersioningFree lesson

Singular vs Plural Resource Names

Choosing between /user/123 and /users/123 and maintaining consistency across your API.

Singular vs Plural Resource Names

You'll learn: How to choose between /user/123 and /users/123 and why consistency matters more than the choice itself.

The Core Question

When designing REST APIs, one of the earliest debates is whether to name collections with singular or plural nouns. Should you fetch a user via /user/123 or /users/123? Should you list all products at /product or /products?

Why It Matters

Resource naming isn't just cosmetic—it affects:

  • Developer intuition: How quickly new API consumers understand your endpoints
  • Code maintainability: Consistent patterns reduce mental overhead
  • Tooling compatibility: Some API frameworks and generators expect specific conventions

The Industry Standard: Plural Wins

The overwhelming convention is plural resource names for collections:

GET    /users           # List all users
GET    /users/123       # Get specific user
POST   /users           # Create new user
DELETE /users/123       # Delete specific user

Think of it like a filing cabinet: the drawer labeled "Users" contains individual user folders. You wouldn't label it "User" even when retrieving one file from it.

The Consistency Principle

Whatever you choose, consistency across your entire API is mandatory. Mixing /user/123 and /products creates cognitive friction and suggests poor design governance.

Some teams use singular for singleton resources (resources with only one instance):

GET /profile    # Current user's profile (only one per session)
GET /users/123  # Any user by ID

Key Takeaway: Use plural resource names (/users/123) as the standard convention for collections, and maintain absolute consistency across your entire API—inconsistency is worse than picking the "wrong" convention.