Avoiding verbs in URLs in Rest API - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ Predict Output

intermediate

REST API URL Design: Identify the Correct Resource URL

Which URL best follows REST API principles by avoiding verbs and focusing on resources?

A /users/create

B /createUser

C /users

D /add-user

💡 Hint

Think about URLs as nouns representing resources, not actions.

REST APIs should use nouns in URLs to represent resources. Actions like 'create' or 'add' are verbs and should be avoided in URLs. Instead, HTTP methods (POST, GET, PUT, DELETE) define the action.

🧠 Conceptual

intermediate

Why Avoid Verbs in REST API URLs?

What is the main reason to avoid verbs in REST API URLs?

A Because HTTP methods already specify the action, so URLs should represent resources

B Because verbs make URLs longer and harder to read

C Because verbs cause security issues in APIs

D Because verbs are not supported by all browsers

💡 Hint

Consider how HTTP methods and URLs work together in REST.

In REST, URLs represent resources (nouns), and HTTP methods (GET, POST, PUT, DELETE) specify the action (verb). This separation keeps APIs clean and consistent.

🔧 Debug

advanced

Identify the Problem with This REST API URL

Look at this URL used in a REST API: /deleteOrder/123. What is the main issue with this URL design?

A It uses a verb 'delete' in the URL instead of relying on HTTP DELETE method

B The order ID should be a query parameter, not part of the URL path

C The URL should be uppercase for better readability

D It should use POST method instead of DELETE

💡 Hint

Think about how REST APIs separate actions from resource paths.

REST APIs should avoid verbs in URLs. The action 'delete' should be expressed by the HTTP DELETE method, while the URL should identify the resource, e.g., /orders/123.

📝 Syntax

advanced

Choose the Correct RESTful URL for Updating a User

Which URL correctly follows RESTful design principles for updating a user with ID 45?

A /updateUser/45

B /users/45

C /users/update/45

D /users?id=45&action=update

💡 Hint

Remember, URLs should represent resources, and HTTP methods specify the action.

The URL should identify the resource (/users/45). The update action is indicated by using the HTTP PUT or PATCH method, not by verbs in the URL.

🚀 Application

expert

Design a REST API URL for Filtering Products by Category

You want to design a REST API URL to get products filtered by category 'electronics'. Which URL follows REST principles best?

A /getElectronicsProducts

B /products/electronics

C /filterProducts/category/electronics

D /products?category=electronics

💡 Hint

Think about how to represent filtering in REST APIs using query parameters.

Filtering is best done using query parameters. The URL /products?category=electronics represents the products resource filtered by category without using verbs.