Batch delete patterns in Rest API

Introduction

Batch delete patterns help remove many items at once using a single request. This saves time and makes your app faster.

You want to delete multiple user accounts at once.

You need to remove many files or records in one go.

You want to clear old data matching certain rules quickly.

You want to reduce the number of requests to the server.

You want to keep your app responsive by deleting in bulk.

Syntax

Rest API

DELETE /resource
{
  "ids": ["id1", "id2", "id3"]
}

OR

DELETE /resource?ids=id1,id2,id3

Batch delete usually uses the HTTP DELETE method.

You can send IDs in the request body or as query parameters, depending on the API design.

Examples

Deletes users with IDs 123, 456, and 789 by sending them in the request body.

Rest API

DELETE /users
{
  "ids": ["123", "456", "789"]
}

Deletes files with IDs abc, def, and ghi by passing IDs in the URL query.

Rest API

DELETE /files?ids=abc,def,ghi

Sample Program

This Python code sends a batch delete request to remove three items by their IDs. It prints success or failure based on the server response.

Rest API

import requests

url = "https://api.example.com/items"

# IDs to delete
ids_to_delete = ["item1", "item2", "item3"]

# Prepare JSON body
payload = {"ids": ids_to_delete}

# Send DELETE request with JSON body
response = requests.delete(url, json=payload)

if response.status_code == 200:
    print("Items deleted successfully")
else:
    print(f"Failed to delete items: {response.status_code}")

Important Notes

Not all APIs support batch delete; check the API docs first.

Some APIs limit how many items you can delete at once.

Always handle errors in case some items cannot be deleted.

Summary

Batch delete removes many items with one request.

Use DELETE method with IDs in body or query.

It saves time and reduces server load.

Practice

1.

What is the main advantage of using batch delete in a REST API?

easy

A. It removes multiple items with a single request, saving time.

B. It automatically backs up data before deletion.

C. It encrypts data during deletion.

D. It requires multiple requests for each item.

Solution

1. Step 1: Understand batch delete purpose

   Batch delete is designed to remove many items at once, not one by one.

2. Step 2: Identify the benefit

   Removing multiple items in one request saves time and reduces server load.

3. Final Answer:

   It removes multiple items with a single request, saving time. -> Option A

4. Quick Check:

   Batch delete = single request for many items [OK]

Hint: Batch delete means one request deletes many items [OK]

Common Mistakes:

• Thinking batch delete backs up data
• Confusing batch delete with encryption
• Assuming batch delete needs multiple requests

2.

Which of the following is the correct HTTP method to perform a batch delete in a REST API?

easy

A. GET

B. POST

C. DELETE

D. PUT

Solution

1. Step 1: Recall HTTP methods for REST

   DELETE method is used to remove resources in REST APIs.

2. Step 2: Match method to batch delete

   Batch delete also uses DELETE but with multiple IDs in body or query.

3. Final Answer:

   DELETE -> Option C

4. Quick Check:

   Batch delete uses DELETE method [OK]

Hint: DELETE method removes resources in REST APIs [OK]

Common Mistakes:

• Using POST instead of DELETE for deletion
• Confusing GET with delete operations
• Using PUT which is for updates

3.

Given this REST API call to delete users with IDs 3, 5, and 7:
DELETE /users?ids=3,5,7
What is the expected behavior?

medium

A. Only user with ID 3 is deleted.

B. Users are deleted one by one with separate requests.

C. The server returns an error because multiple IDs are not allowed.

D. Users with IDs 3, 5, and 7 are deleted in one request.

Solution

1. Step 1: Analyze the query parameter usage

   The query parameter 'ids=3,5,7' lists multiple IDs to delete.

2. Step 2: Understand batch delete behavior

   The API deletes all specified users in one DELETE request.

3. Final Answer:

   Users with IDs 3, 5, and 7 are deleted in one request. -> Option D

4. Quick Check:

   Batch delete with multiple IDs = one request deletes all [OK]

Hint: Multiple IDs in query means batch delete in one request [OK]

Common Mistakes:

• Assuming only first ID is deleted
• Thinking server rejects multiple IDs
• Believing multiple requests are sent automatically

4.

Consider this batch delete request:
DELETE /items
with JSON body:
{ "ids": [10, 20, 30] }
But the server responds with 400 Bad Request. What is the likely cause?

medium

A. The JSON format is incorrect.

B. The server expects IDs in the query string, not body.

C. The DELETE method cannot have a request body.

D. The IDs array is empty.

Solution

1. Step 1: Check DELETE method usage

   Some APIs require IDs in query string, not in request body for DELETE.

2. Step 2: Identify server expectation

   Since server returns 400, it likely expects IDs in query parameters, not JSON body.

3. Final Answer:

   The server expects IDs in the query string, not body. -> Option B

4. Quick Check:

   Server expects IDs in query, not body [OK]

Hint: Check if server wants IDs in query or body for DELETE [OK]

Common Mistakes:

• Assuming DELETE cannot have a body always
• Thinking JSON format is wrong without checking
• Ignoring server API documentation

5.

You want to design a batch delete endpoint for a REST API that deletes multiple products by IDs sent in the request body as JSON. Which approach is best practice?

{
  "ids": [101, 102, 103]
}

Choose the correct method and request format.

hard

A. Use DELETE method with JSON body containing IDs array.

B. Use POST method with JSON body containing IDs array.

C. Use DELETE method with IDs in query string separated by commas.

D. Use GET method with IDs in URL path.

Solution

1. Step 1: Understand REST conventions for delete

   DELETE method is standard for removing resources, including batch deletes.

2. Step 2: Check request body usage

   Modern APIs allow DELETE with JSON body to specify multiple IDs for batch delete.

3. Step 3: Evaluate options

   POST is not for deletion, GET is for retrieval, query string can be limited in length.

4. Final Answer:

   Use DELETE method with JSON body containing IDs array. -> Option A

5. Quick Check:

   DELETE + JSON body for batch delete = best practice [OK]

Hint: Use DELETE with JSON body for multiple IDs batch delete [OK]

Common Mistakes:

• Using POST instead of DELETE for deletion
• Putting IDs in query string risking URL length limits
• Using GET which is not for deletion