In a RESTful API, how you respond to a client is just as important as what you respond with. In Django REST Framework (DRF), the Response class and HTTP status codes are essential tools for clearly communicating the outcome of an API request.

This guide will help you understand:

• What the Response class is

• Why status codes matter

• Common status codes used in APIs

• How to use them effectively in DRF

• Best practices and common mistakes

What is Response in DRF?

In DRF, the Response class is a subclass of Django's HttpResponse, but it's designed for APIs. It:

• Automatically renders content into the right format (e.g. JSON)

• Supports content negotiation

• Works seamlessly with DRF’s request/response flow

✅ Basic Example

from rest_framework.response import Response

def example_view(request):
    return Response({"message": "Hello, API!"})

Behind the scenes, DRF converts this into a JSON response:

{
  "message": "Hello, API!"
}

Why Are Status Codes Important?

HTTP status codes tell the client what happened. They are standardized and widely understood by frontends, mobile apps, and even humans.

How to Use Status Codes in DRF

DRF provides a handy module: rest_framework.status

✅ Example with Status Codes

from rest_framework.views import APIView
from rest_framework.response import Response
from rest_framework import status

class ExampleView(APIView):
    def get(self, request):
        return Response({"message": "All good"}, status=status.HTTP_200_OK)

    def post(self, request):
        if "name" not in request.data:
            return Response({"error": "Name is required"}, status=status.HTTP_400_BAD_REQUEST)
        return Response({"message": "Created"}, status=status.HTTP_201_CREATED)

Real Example: Handling All Statuses

class BookDetailView(APIView):
    def get(self, request, pk):
        try:
            book = Book.objects.get(pk=pk)
        except Book.DoesNotExist:
            return Response({"error": "Not found"}, status=status.HTTP_404_NOT_FOUND)
        serializer = BookSerializer(book)
        return Response(serializer.data, status=status.HTTP_200_OK)

    def delete(self, request, pk):
        try:
            book = Book.objects.get(pk=pk)
            book.delete()
            return Response(status=status.HTTP_204_NO_CONTENT)
        except Book.DoesNotExist:
            return Response({"error": "Not found"}, status=status.HTTP_404_NOT_FOUND)

When to Use Which Status Code

⚠️ Common Mistakes

Best Practices

• ✅ Always return appropriate status codes — it improves client-side logic and debugging.

• ✅ Use DRF’s status module instead of hardcoding numbers (more readable).

• ✅ Return useful error messages with 400, 404, 403, etc.

• ✅ Avoid 500 errors by handling exceptions with try/except.

Summary

A well-designed API not only sends back data, but also sends back the right message using HTTP status codes.