Why Resource identifiers in URLs in Rest API? - Purpose & Use Cases

The Big Idea

What if you could instantly find any item online just by its unique address?

The Scenario

Imagine you want to find a specific book in a huge library, but there is no catalog or system to locate it. You have to ask around or search shelf by shelf.

The Problem

Without clear resource identifiers in URLs, APIs become like that library without a catalog. Finding or updating a specific item means guessing or sending many requests, which is slow and confusing.

The Solution

Using resource identifiers in URLs is like giving each book a unique shelf label. You can directly ask for the exact item you want, making communication fast and clear.

Before vs After

✗ Before

GET /books?title=Harry Potter&author=Rowling
GET /books
POST /books/12345/update

✓ After

GET /books/12345
PUT /books/12345
DELETE /books/12345

What It Enables

This makes APIs simple and powerful, letting you directly access, update, or delete any resource with a clear and consistent address.

Real Life Example

When you shop online, each product has a unique URL. This lets you share, bookmark, or buy that exact product without confusion.

Key Takeaways

Resource identifiers give each item a unique address.

They make API requests clear and efficient.

They help developers and users find exactly what they need quickly.

Practice

1. What is the main purpose of resource identifiers in REST API URLs?

easy

A. To uniquely identify a specific resource

B. To specify the HTTP method used

C. To define the server address

D. To set the response format

Solution

1. Step 1: Understand resource identifiers

   Resource identifiers are unique parts of a URL that point to a specific item or resource.

2. Step 2: Identify their role in REST APIs

   They help the server know exactly which resource the client wants to access or modify.

3. Final Answer:

   To uniquely identify a specific resource -> Option A

4. Quick Check:

   Resource identifiers = unique resource ID [OK]

Hint: Resource IDs point to one item in the URL [OK]

Common Mistakes:

• Confusing resource identifiers with HTTP methods
• Thinking resource identifiers define server location
• Mixing resource identifiers with response formats

2. Which of the following is the correct way to include a resource identifier for a user with ID 42 in a REST API URL?

easy

A. /users#42

B. /users?id=42

C. /users/42/details

D. /users/42

Solution

1. Step 1: Identify the standard REST URL format

   Resource identifiers usually come directly after the resource name separated by a slash.

2. Step 2: Check each option

   /users/42 uses "/users/42" which correctly places the ID after the resource name. /users?id=42 uses a query parameter, which is less common for resource identification. /users/42/details adds extra path which may refer to a sub-resource. /users#42 uses a fragment which is not for resource IDs.

3. Final Answer:

   /users/42 -> Option D

4. Quick Check:

   Resource ID follows resource name with slash [OK]

Hint: Resource ID follows resource name with a slash / [OK]

Common Mistakes:

• Using query parameters instead of path segments
• Adding extra path parts that change meaning
• Using URL fragments (#) for resource IDs

3. Given the URL /products/123/reviews/456, which resource does the identifier 456 represent?

medium

A. Product with ID 456

B. Review with ID 456 for product 123

C. Product with ID 123

D. All reviews for product 456

Solution

1. Step 1: Break down the URL path

   The URL has two resource names: "products" and "reviews" with IDs 123 and 456 respectively.

2. Step 2: Understand the hierarchy

   "reviews/456" comes after "products/123", so 456 is the review ID related to product 123.

3. Final Answer:

   Review with ID 456 for product 123 -> Option B

4. Quick Check:

   Last ID is for last resource in URL [OK]

Hint: Last ID belongs to the last resource named [OK]

Common Mistakes:

• Mixing IDs and thinking 456 is a product ID
• Ignoring resource hierarchy in URL
• Assuming IDs apply to all resources

4. Identify the error in this REST API URL for accessing order 789: /orders/ 789

medium

A. The resource identifier should be before the resource name

B. There should be no slash between resource name and ID

C. The ID should be part of the path, not separate

D. The URL is correct as is

Solution

1. Step 1: Analyze the URL structure

   The URL shows /orders/ and then 789 separately, which suggests the ID is not part of the path.

2. Step 2: Understand correct resource ID placement

   The ID should be directly after the resource name in the same path segment, like /orders/789.

3. Final Answer:

   The ID should be part of the path, not separate -> Option C

4. Quick Check:

   Resource ID must be in the path segment [OK]

Hint: Resource ID must be in the same path segment [OK]

Common Mistakes:

• Placing ID outside the URL path
• Removing the slash between resource and ID
• Thinking resource ID comes before resource name

5. You want to design a REST API URL to access a comment with ID 555 on a post with ID 101. Which URL correctly uses resource identifiers to reflect this nested relationship?

hard

A. /posts/101/comments/555

B. /comments/555/posts/101

C. /posts/comments/555/101

D. /posts/555/comments/101

Solution

1. Step 1: Understand resource hierarchy

   The comment belongs to a post, so the post resource should come first in the URL.

2. Step 2: Check each URL option

   /posts/101/comments/555 correctly places the post ID first, then the comments resource with its ID. Other options mix the order or IDs incorrectly.

3. Final Answer:

   /posts/101/comments/555 -> Option A

4. Quick Check:

   Parent resource ID before child resource ID [OK]

Hint: Parent resource ID comes before child resource ID in URL [OK]

Common Mistakes:

• Reversing parent and child resource order
• Mixing IDs between resources
• Placing IDs in wrong path segments