Plural vs singular resource names in Rest API - Interactive Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to define the endpoint for retrieving all users.

Rest API

GET /[1]

Drag options to blanks, or click blank then click option'

Ausers

Buser

Cprofile

Daccount

Attempts:

3 left

💡 Hint

Common Mistakes

Using singular form for a collection endpoint like /user instead of /users.

The endpoint should use the plural form users to represent the collection of user resources.

2fill in blank

medium

Complete the code to define the endpoint for retrieving a single user by ID.

Rest API

GET /users/[1]

Drag options to blanks, or click blank then click option'

Aall

Bid

C{id}

D123

Attempts:

3 left

💡 Hint

Common Mistakes

Using a fixed number like 123 instead of a variable placeholder.

Using 'id' without curly braces.

The endpoint should use a path parameter {id} to specify the user ID dynamically.

3fill in blank

hard

Fix the error in the endpoint for creating a new user.

Rest API

POST /[1]

Drag options to blanks, or click blank then click option'

Auser

Busers

Cuser/{id}

Dusers/{id}

Attempts:

3 left

💡 Hint

Common Mistakes

Including an ID in the URL for POST requests to create resources.

To create a new user, the endpoint should be the plural resource name users without an ID.

4fill in blank

hard

Fill both blanks to define the endpoint for updating a user's profile.

Rest API

PUT /[1]/[2]/profile

Drag options to blanks, or click blank then click option'

Ausers

Buser

C{userId}

Did

Attempts:

3 left

💡 Hint

Common Mistakes

Using singular resource name for the collection.

Using a fixed string like 'id' instead of a parameter.

The endpoint uses the plural resource users and a path parameter {userId} to specify which user to update.

5fill in blank

hard

Fill all three blanks to define the endpoint for deleting a specific order item.

Rest API

DELETE /[1]/[2]/[3]

Drag options to blanks, or click blank then click option'

Aorders

B{orderId}

Citems

D{itemId}

Attempts:

3 left

💡 Hint

Common Mistakes

Using singular resource names instead of plural.

Using fixed strings instead of parameters for IDs.

The endpoint uses plural orders, a path parameter {orderId}, and a path parameter {itemId} to delete a specific item in an order.

Practice

1. Which naming style is recommended for an API endpoint that returns a list of users?
/user or /users?

easy

A. /users because it is singular and more precise.

B. /user because it is shorter and simpler.

C. /user because it is singular and more precise.

D. /users because it represents multiple users.

Solution

1. Step 1: Understand resource naming for collections

   API endpoints returning multiple items should use plural names to clearly indicate a list.

2. Step 2: Apply naming to the example

   Since the endpoint returns multiple users, /users is the correct plural form.

3. Final Answer:

   /users because it represents multiple users. -> Option D

4. Quick Check:

   Plural for lists = /users [OK]

Hint: Use plural names for endpoints returning lists [OK]

Common Mistakes:

• Using singular for list endpoints
• Confusing singular and plural forms
• Choosing shorter names over clarity

2. Which of the following is the correct endpoint to access a single product by its ID?

easy

A. /products/123

B. /product/123

C. /products

D. /product

Solution

1. Step 1: Identify singular vs plural for single item access

   When accessing a single item by ID, use the plural form of the resource name followed by the ID.

2. Step 2: Match the correct endpoint format

   The endpoint /products/123 uses plural products and includes the ID, which is the common RESTful convention.

3. Final Answer:

   /products/123 -> Option A

4. Quick Check:

   Single item access = plural + ID [OK]

Hint: Use plural resource name when accessing one item by ID [OK]

Common Mistakes:

• Using singular resource name for single item
• Omitting the ID when accessing a single item
• Mixing singular/plural inconsistently

3. Given the following API endpoints, which one correctly retrieves a list of orders?

GET /order
GET /orders
GET /order/456
GET /orders/456

medium

A. GET /order

B. GET /orders/456

C. GET /orders

D. GET /order/456

Solution

1. Step 1: Identify endpoints returning lists

   Endpoints returning lists should use plural resource names without an ID.

2. Step 2: Analyze each option

   GET /orders uses plural and no ID, so it returns the list of orders. Others either use singular or include an ID, indicating single item access.

3. Final Answer:

   GET /orders -> Option C

4. Quick Check:

   List retrieval = plural resource without ID [OK]

Hint: Plural + no ID means list retrieval [OK]

Common Mistakes:

• Choosing singular endpoint for list
• Confusing ID presence with list retrieval
• Ignoring plural vs singular rules

4. You have an API endpoint defined as GET /users/ to get a list of users and GET /user/{id} to get a single user. A developer mistakenly uses GET /user/ to get all users. What is the likely problem?

medium

A. The endpoint /user/ is incorrect for list retrieval and may cause a 404 error.

B. The endpoint /user/ will return a list of users anyway.

C. The endpoint /user/ will return a single user without ID.

D. The endpoint /user/ will automatically redirect to /users/.

Solution

1. Step 1: Understand endpoint naming conventions

   List retrieval requires plural resource name, so /users/ is correct for all users.

2. Step 2: Analyze the incorrect usage

   /user/ is singular and without an ID, so it likely does not exist or returns an error like 404.

3. Final Answer:

   The endpoint /user/ is incorrect for list retrieval and may cause a 404 error. -> Option A

4. Quick Check:

   Singular without ID ≠ list endpoint [OK]

Hint: Singular without ID usually causes errors for list requests [OK]

Common Mistakes:

• Using singular endpoint for list retrieval
• Assuming singular endpoint returns list
• Expecting automatic redirects between endpoints

5. You are designing an API for a library system. Which of the following endpoint designs correctly follows the plural vs singular resource naming best practices for retrieving a single book and all books?

hard

A. GET /book for all books and GET /books/{id} for a single book

B. GET /books for all books and GET /book/{id} for a single book

C. GET /books/{id} for all books and GET /book for a single book

D. GET /book/{id} for all books and GET /books for a single book

Solution

1. Step 1: Recall naming rules for collections and single items

   Use plural resource names for collections (all books) and singular for single items by ID.

2. Step 2: Match options to rules

   GET /books correctly retrieves all books (plural). GET /book/{id} correctly retrieves a single book (singular with ID).

3. Final Answer:

   GET /books for all books and GET /book/{id} for a single book -> Option B

4. Quick Check:

   Plural for list, singular + ID for single [OK]

Hint: Plural for lists, singular + ID for single items [OK]

Common Mistakes:

• Swapping singular and plural for list vs single
• Using singular without ID for list
• Using plural with ID for single item