Skip to main content
2026-07-29 16:01
REST API

DELETE User

RequestValidateErrorEasy
Try Interactive Demo

What you will learn

  • Decide between 204 No Content and 200 with body — contract consistency matters
  • Verify idempotency: a second DELETE of the same resource should not error unexpectedly
  • Check cascade behaviour: does deleting a user leave orphaned posts / orders?

Description

Delete a user by ID. Verify successful deletion and 404 on subsequent access.

Test Scenario

const response = await request.delete('/api/v1/users/1');
expect(response.status()).toBe(204);
// Verify deleted
const check = await request.get('/api/v1/users/1');
expect(check.status()).toBe(404);
Endpoint/api/v1/users/:id

Testing Tips

  • •Check 204 No Content on success
  • •Verify GET returns 404 after delete
  • •Handle already-deleted resources
// Playwright - DELETE user
import { test, expect } from '@playwright/test';


test('DELETE /api/v1/users/:id', async ({ request }) => {
  // First create a user to delete
  const createResponse = await request.post('/api/v1/users', {
    data: { name: 'To Delete', email: 'delete@example.com' }
  });
  const { id } = await createResponse.json();


  // Delete the user
  const deleteResponse = await request.delete(`/api/v1/users/${id}`);
  expect(deleteResponse.status()).toBe(204);


  // Verify user is deleted
  const getResponse = await request.get(`/api/v1/users/${id}`);
  expect(getResponse.status()).toBe(404);
});

Challenge ID: rest-delete-user

2 frameworks available

API Playground

Send requests and inspect responses

Endpoint: /api/v1/users/:id

Press Enter to send