Imagine you are building an API with admin authentication. The kinds of auth endpoints you create will depend a lot on your app’s flow and needs.
Any time I look at a UI design or wireframe, I try to identify what endpoints are visibly needed. If it’s an admin authentication flow, the basics usually look like:
POST /signup
POST /verify-otp
POST /login
POST /forgot-password
POST /reset-password
But I don’t stop there. I always ask myself:
“What backend endpoints don’t appear on the UI but are still crucial for secure and smooth functionality?”
Sometimes I go blank, but that’s normal. In those moments, I just tell my AI assistant how I envision the project or hit up a dev friend in my DMs. If I’m working on something like a Student Management System, I usually break it down into categories:
- Admin authentication
- Lesson creation
- Student enrollment, etc.
I either list what I think should be in that category and ask if I missed something, or I just ask, “What else would you add or recommend if given the chance?” You’d be surprised the gems you get back from those convos.
Doing this helps me build endpoints more intentionally, with security, scalability, and clean structure in mind.
Oh, and something I keep reminding myself:
It doesn’t have to be perfect before your first GitHub push... or the second... or the twelfth.
Interestingly, this week, I’ve been working on an auth workflow and was given a recommended list of endpoints to build. That alone made things feel so much clearer. Isn’t that cute? 😄
And funnily enough, that recommended list also opened my eyes to other useful endpoints, like:
POST /resend-verification-otp
POST /change-password
Sometimes, all it takes is a prompt from someone else, or a nudge from an AI to unlock that next layer of clarity.☺️
Progress over perfection. Always. Because even the most polished production apps didn’t start perfect. They evolved. Step by step. Tweak by tweak.
Top comments (0)