Atom GPS Tracking

Built for fleet operators

Track drivers on the map, ingest GPS hardware, and export insights — all from one backend.

WebSocket updates push new coordinates to company and driver dashboards as soon as GPS data is ingested.

Physical trackers connect over TCP (default port 9000). IMEI maps to each driver's gpsDeviceId.

Availability, routes, overspeed events, and scheduled PDF/Excel delivery for your fleet.

JWT-authenticated REST endpoints for drivers, positions, and company administration.

This host serves the HTTP API on port 9092. Trackers use a separate TCP port so devices are not confused with the web API.

Hardware tracker
GT06 protocol → TCP port 9000 on this server's IP.
Mobile test (optional)
POST /api/gps/sim with JSON coordinates when HTTP sim is enabled.
Dashboard
Fleet web app calls /api/* with a login token for maps and history.

Server endpoints

Welcome (this page) /

REST API /api/

Auth POST /api/auth/login

GPS TCP (devices) port 9000

WebSocket /ws

Authenticate to use protected routes. Example login (JSON):

POST /api/auth/login
Content-Type: application/json

{
  "username": "your-user",
  "password": "your-password"
}

Use the returned JWT as Authorization: Bearer <token> on requests such as GET /api/drivers.

Open your company dashboard frontend (Next.js) and point it at this server's base URL for API and WebSocket.

If you only see JSON errors on other paths, that route requires login — this page is public.