Get Current User (Protected Routes Access)

Frontend includes JWT access token as part of Authorization header(Bearer: Token) for API requests

Backend uses @jwt_required() to protect routes

If the token is valid, and not expired/blacklisted, request proceeds, otherwise reject.

Gets user id from JWT token

Queries db for user with user id

Checks if user exists

Onboarding Completion Check

Checks if onboarding required fields are complete

if complete, then user's onboarding status marked complete and commits to db

Returns JSON response with user's ID, name, username, email, onboarding step/status, budget profile.

ALLOWS logged-in users to fetch their profile/budget data and update onboarding status if required fields met.

Request