Uber API is a production-ready ride-hailing backend covering the full journey from authentication to ride completion. Users and captains get separate auth flows, real-time location tracking keeps drivers visible on the map, and every ride moves through a verified lifecycle — fare estimate, confirmation, OTP start, and end.

The problem: Most ride-hailing tutorials fake the hard parts. I wanted to build all of them — multi-role auth, real-time location, Maps API integration, and a complete ride lifecycle — end to end, in one clean backend.

What I built:

— JWT + bcrypt authentication for two actor types (users and captains) with role-specific middleware

— Real-time captain location broadcast via Socket.IO

— Maps API integration: coordinate lookup, distance + ETA calculation, and address autocomplete

— Full ride lifecycle: create request → get fare → captain confirms → OTP-verified start → end ride

— 14 REST endpoints across 4 route groups (/users, /captain, /maps, /rides)

— React (Vite) frontend for interacting with the API

Impact: 14 fully functional endpoints. Two-actor auth system working end-to-end. Real-time location broadcast and OTP-secured ride handoff both verified in production.

Stack: Node.js · Express.js · MongoDB Atlas · Mongoose · JWT · bcrypt · Socket.IO · Maps API · React