Sign in with Google through your backend
FreeSystem map@rabbinatix/social-login-architecture by Rabbinatixupdated Oct 13, 2026
Your backend swaps the code Google sends back for the person’s profile, then starts its own session.
3 systems and 4 APIs. Every API is declared on both sides, so every contract starts healthy. Rename or change anything once it is on your map.
2 connections · 4 APIs
- Web App → Backend API
POST /api/v1/auth/googleFinish signing in with GoogleGET /api/v1/meThe signed-in user
- Backend API → Google OAuth
POST /tokenSwap the sign-in code for tokensGET /v1/userinfoThe Google profile
Systems (3)
Web App
Shows the “Sign in with Google” button.
Backend API
Finishes the sign-in and keeps the session.
Google OAuth
Google’s sign-in service.
A system you already have under the same name is used, not copied. Outside APIs don't count towards your plan.
Also as a flow
Also as a whiteboard
Versions
