Why URL structure communicates meaning in Rest API - Test Your Understanding

Practice - 5 Tasks

1fill in blank

easy

Complete the code to define a REST API endpoint that retrieves all users.

Rest API

GET /[1]

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

Afetch_all

BgetUsers

Cusers

Dlist

Attempts:

3 left

💡 Hint

Common Mistakes

Using verbs like 'getUsers' in the URL instead of resource names.

The URL /users clearly indicates the resource being accessed, which is the collection of users.

2fill in blank

medium

Complete the URL to access a specific user by their ID.

Rest API

GET /users/[1]

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

Aname

Btype

Caction

Did

Attempts:

3 left

💡 Hint

Common Mistakes

Using generic terms like 'name' or 'type' which may not uniquely identify a user.

The URL uses id to specify a unique user resource, making the URL meaningful and precise.

3fill in blank

hard

Fix the error in the URL that tries to update a user's email.

Rest API

PUT /users/[1]/updateEmail

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

Aid

Bupdate

Cemail

Duser

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'updateEmail' as part of the URL path instead of relying on HTTP PUT method.

The URL should include the user's id to specify which user to update. The action updateEmail is better handled by HTTP method semantics rather than in the URL.

4fill in blank

hard

Fill both blanks to create a URL that lists all orders for a specific user.

Rest API

GET /[1]/[2]/orders

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

Ausers

Bproducts

C123

Dorders

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'products' or 'orders' in the wrong place in the URL.

The URL /users/123/orders clearly shows orders belonging to user with ID 123, making the URL meaningful and hierarchical.

5fill in blank

hard

Fill all three blanks to create a URL that accesses a specific comment on a post by a user.

Rest API

GET /[1]/[2]/posts/[3]/comments

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

Ausers

B456

C789

Dposts

Attempts:

3 left

💡 Hint

Common Mistakes

Mixing up the order of user and post IDs or using wrong resource names.

The URL /users/456/posts/789/comments clearly shows comments on post 789 by user 456, making the URL structure meaningful and easy to understand.

Practice

1. Why is it important for a REST API URL to have a clear and meaningful structure?

easy

A. It makes the URL longer and more complex.

B. It helps users and developers understand what data or resource the URL points to.

C. It hides the resource details from users.

D. It prevents the API from working on mobile devices.

Solution

1. Step 1: Understand URL purpose in REST API

   The URL should clearly indicate the resource or data it represents to make it easy to use.

2. Step 2: Analyze the options

   Only It helps users and developers understand what data or resource the URL points to. states that clear URLs help users and developers understand the resource, which is the main goal.

3. Final Answer:

   It helps users and developers understand what data or resource the URL points to. -> Option B

4. Quick Check:

   Meaningful URLs improve understanding = A [OK]

Hint: Clear URLs describe the resource directly [OK]

Common Mistakes:

• Thinking longer URLs are better
• Believing URLs should hide resource info
• Assuming URL structure affects device compatibility

2. Which of the following is the correct way to structure a REST API URL for accessing a user's orders?

easy

A. /user/123/orders

B. /orders/user/123

C. /123/orders/user

D. /orders/123user

Solution

1. Step 1: Identify the resource hierarchy

   The URL should start with the main resource (user), then the specific user ID, then the sub-resource (orders).

2. Step 2: Check each option

   /user/123/orders follows the pattern /user/{id}/orders, which is clear and standard. Others mix order or combine parts incorrectly.

3. Final Answer:

   /user/123/orders -> Option A

4. Quick Check:

   Resource then ID then sub-resource = A [OK]

Hint: Put main resource before ID and sub-resource [OK]

Common Mistakes:

• Placing ID before resource name
• Mixing resource and ID order
• Combining ID and resource without separator

3. Given the URL /products/45/reviews, what does this URL most likely represent?

medium

A. All products and their reviews

B. Product number 45's details only

C. Reviews for the product with ID 45

D. A list of all reviews without product info

Solution

1. Step 1: Break down the URL parts

   /products indicates the main resource, 45 is the product ID, and /reviews is a sub-resource related to that product.

2. Step 2: Interpret the meaning

   The URL points to reviews specifically for product 45, not all products or unrelated reviews.

3. Final Answer:

   Reviews for the product with ID 45 -> Option C

4. Quick Check:

   Sub-resource after ID means related data = C [OK]

Hint: Sub-resource after ID means related data for that item [OK]

Common Mistakes:

• Thinking it lists all products
• Confusing product details with reviews
• Ignoring the product ID in URL

4. A developer wrote the URL /users//123/orders to get orders for user 123. What is the problem with this URL?

medium

A. The URL is missing a query parameter.

B. User ID should come after orders, not before.

C. Orders should be capitalized in the URL.

D. Double slashes cause incorrect URL structure and may lead to errors.

Solution

1. Step 1: Examine the URL structure

   The URL has two slashes between 'users' and '123', which is not standard and can cause parsing issues.

2. Step 2: Evaluate the impact

   Double slashes can confuse servers or clients, leading to errors or unexpected behavior.

3. Final Answer:

   Double slashes cause incorrect URL structure and may lead to errors. -> Option D

4. Quick Check:

   Extra slashes break URL format = D [OK]

Hint: Avoid double slashes in URLs [OK]

Common Mistakes:

• Ignoring extra slashes
• Thinking order of ID and resource is wrong here
• Believing capitalization matters in URLs

5. You want to design a REST API URL to get all comments for a specific post by a user. Which URL structure best communicates this meaning?

hard

A. /user/789/post/456/comments

B. /comments/user/789/post/456

C. /post/456/comments/user/789

D. /comments/post/456/user/789

Solution

1. Step 1: Identify the resource hierarchy

   The main resource is the user, then the specific post by that user, then the comments on that post.

2. Step 2: Check URL clarity and order

   /user/789/post/456/comments follows the logical order: user ID, post ID, then comments, making it clear and meaningful.

3. Step 3: Eliminate confusing options

   Other options mix order or place comments before user/post, which is less clear.

4. Final Answer:

   /user/789/post/456/comments -> Option A

5. Quick Check:

   Parent resource then child then sub-resource = B [OK]

Hint: Order URL from general to specific resource [OK]

Common Mistakes:

• Mixing resource order
• Placing comments before user/post
• Ignoring resource hierarchy