Robot Fleet Management Backend & Dashboard

I have designed the mission dispatch schema and API endpoints. The system uses idempotency keys to prevent duplicate missions and includes fields for real-time telemetry updates.

Mission Dispatch API Design

Data Schema (PostgreSQL)

API Endpoints (v1)

openapi: 3.0.0
paths:
  /missions:
    post:
      summary: Dispatch a new mission
      parameters:
        - in: header
          name: X-Idempotency-Key
          required: true
          schema:
            type: string
      requestBody:
        content:
          application/json:
            schema:
              type: object
              properties:
                robot_id: { type: string, format: uuid }
                task_data: { type: object }
      responses:
        '201':
          description: Mission created
  /robots/{id}/status:
    get:
      summary: Get live battery and GPS
      responses:
        '200':
          content:
            application/json:
              schema:
                type: object
                properties:
                  battery: { type: integer }
                  lat: { type: number }
                  lng: { type: number }
                  last_seen: { type: string, format: date-time }

Next steps

1. Implement the MQTT bridge to sync robots.location from hardware to the database.
2. Configure the RBAC middleware to ensure tenants only see their own fleet.
3. Set up the event worker to handle mission.status transitions.