<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>secure django api on Kuldeep Pisda</title><link>https://kdpisda.in/tag/secure-django-api/</link><description>Recent content in secure django api on Kuldeep Pisda</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Tue, 23 Dec 2025 10:46:20 +0530</lastBuildDate><atom:link href="https://kdpisda.in/tag/secure-django-api/index.xml" rel="self" type="application/rss+xml"/><item><title>A Pragmatic Django REST Framework Tutorial for Real World APIs</title><link>https://kdpisda.in/a-pragmatic-django-rest-framework-tutorial-for-real-world-apis/</link><pubDate>Sat, 20 Dec 2025 15:23:15 +0530</pubDate><guid>https://kdpisda.in/a-pragmatic-django-rest-framework-tutorial-for-real-world-apis/</guid><description>&lt;p&gt;So you&amp;rsquo;ve built a killer Django application. The models are tight, the admin is humming, and your server side templates are doing exactly what they should. Then, the inevitable happens.&lt;/p&gt;
&lt;p&gt;Someone asks, &amp;ldquo;Hey, can we get an API for the new mobile app?&amp;rdquo; Or maybe you&amp;rsquo;re itching to plug in a modern frontend like React or Vue. Suddenly, just serving up HTML isn&amp;rsquo;t going to cut it anymore.&lt;/p&gt;
&lt;p&gt;This is a classic crossroads for a Django developer. I&amp;rsquo;ve been there. The first time I hit this wall, I remember spending hours just trying to figure out how to wrestle my perfectly good Django models into clean, predictable JSON. I tried building the JSON responses by hand, which I now know is a nightmare I recommend everyone avoid. The whole concept of a &amp;ldquo;serializer&amp;rdquo; felt like some kind of dark art.&lt;/p&gt;</description></item></channel></rss>