Plural vs singular resource names in Rest API - Quick Revision & Key Differences

Recall & Review

beginner

Why do REST APIs usually use plural resource names?

Plural resource names represent collections of items, making it clear that the endpoint deals with multiple resources, like /users for many users.

beginner

What does a singular resource name usually represent in REST APIs?

A singular resource name often represents a single item or entity, typically used in the URL when accessing or modifying one specific resource, like /users/123.

beginner

Which is the recommended way to name a resource collection endpoint: /book or /books?

The recommended way is /books because it clearly indicates a collection of book resources.

beginner

How would you name an endpoint to get a single user by ID?

Use the plural resource name followed by the ID, like /users/123, to indicate you want one user from the users collection.

intermediate

Is it okay to mix singular and plural resource names in the same API?

It is best to be consistent and use plural names for collections and singular only when referring to a single resource by ID. Mixing can confuse users and developers.

Which URL is best for accessing all products in a REST API?

A /products

B /product

C /getProducts

D /allproducts

Using the plural noun /products clearly indicates a collection of product resources.

How should you name the endpoint to update a single order with ID 45?

A /order/45

B /orders/update/45

C /orders/45

D /updateOrder/45

Use the plural resource name with the ID: /orders/45 to target one order.

Why avoid using singular resource names for collection endpoints?

A They confuse the meaning of the endpoint

B They require more server memory

C They are slower to load

D They are harder to type

Singular names suggest a single item, so using them for collections can confuse users about what the endpoint returns.

Which is the best practice for REST API resource naming?

A Use uppercase letters in URLs

B Use singular for all endpoints

C Use verbs in resource names

D Use plural for collections and singular for single items

Plural names for collections and singular for single items keep the API clear and consistent.

What does the URL /users/789 typically represent?

A A collection of users

B A single user with ID 789

C A search for users

D An error page

The plural users followed by an ID usually means one user resource.

Explain why REST APIs prefer plural resource names for collections and how singular names are used.

Think about how you talk about groups vs. one item in real life.

Describe the potential confusion if singular resource names are used for collections in REST APIs.

Imagine asking for 'book' but getting many books instead.