How I Safely Added New Fields to My Django API Without Breaking Existing Users (Inboxit Case Study)

While building Inboxit a plug-and-play tool that forwards website form submissions to email, Slack, or WhatsApp, I needed to add new fields and change serializers to support more features. The API was already live in production with real users. Changing models and serializers risked breaking existing integrations. Here’s exactly how I handled it using the Expand-Contract pattern and API versioning. The Situation I had to add new fields to the main model. At the same time, I wanted to improve the response structure. If I just updated the existing serializer, all current integrations would break. My Approach: API Versioning + Expand-Contract I decided to introduce v2 while keeping v1 fully functional. Step 1: Expand Added the new fields to the Django model (kept the old fields intact). Here’s what the model looked like after adding the new fields: Step 2: Versioning in URLs I set up URL versioning so both versions could coexist: # urls.py urlpatterns = [ path ( ' api/v1/ ' , include ( '