LivePin Logo

Reports & Fleet Operations API

Livepin reporting endpoints provide operational, compliance, and utilization insights for single vehicles and full fleets. Fleet operations endpoints cover day-to-day setup and automation primitives: grouping vehicles, assigning driver records, geofence management, and alert preferences.

Report families

  • Name
    Distance
    Description

    /km-report, route summary, interval reports.

  • Name
    Engine/Activity
    Description

    moving, stopped, idle, parked, engine-on, ignition.

  • Name
    Geofence
    Description

    entry/exit report versions and reverse geocode helpers.

  • Name
    Fuel
    Description
    fuel fillup, fuel summary, fuel consumption.
  • Name
    Exceptions
    Description
    no-data and overspeed diagnostics.

Vehicle reports

  • Name
    GET /api/vehicles/:id/daily-summary-report
    Description
    Daily summary for one vehicle.
  • Name
    GET /api/vehicles/:id/route-summary-report
    Description
    Route level summary for date.
  • Name
    GET /api/vehicles/:id/single-vehicle-history-report
    Description
    Detailed path/timeline report.
  • Name
    GET /api/vehicles/:id/fuel-fillup-report
    Description
    Fuel fill-up events.
  • Name
    GET /api/vehicles/:id/overspeed-report
    Description
    Overspeed events.
  • Name
    GET /api/vehicles/:id/interval-report
    Description
    Interval based snapshots at 15/30/60/12 min intervals.
  • Name
    GET /api/vehicles/:id/fuel-summary-report
    Description
    Fuel summary overview.
  • Name
    GET /api/vehicles/:id/ignition-report
    Description
    Ignition timeline.

KM report

GET
/api/vehicles/reports/km-report
curl "$LIVEPIN_API_BASE_URL/api/vehicles/reports/km-report" \
  -H "Authorization: Bearer $JWT_TOKEN"

Daily summary (PDF)

GET
/api/vehicles/:id/daily-summary-report
curl -G "$LIVEPIN_API_BASE_URL/api/vehicles/:vehicleId/daily-summary-report" \
  -H "Authorization: Bearer $JWT_TOKEN" \
  -d start_date=1/10/2025 \
  -d end_date=12/10/2025 \
  -d format=pdf

Interval report

GET
/api/vehicles/:id/interval-report
curl -G "$LIVEPIN_API_BASE_URL/api/vehicles/:vehicleId/interval-report" \
  -H "Authorization: Bearer $JWT_TOKEN" \
  -d interval=30 \
  -d start_timestamp=1732080473000 \
  -d end_timestamp=1732080473000

Fleet reports

General fleet reports

  • Name
    GET /api/vehicles/all-daily-summary-report
    Description

    All vehicles daily summary.

  • Name
    GET /api/vehicles/all-daily-activity-report
    Description

    Fleet activity dashboard feed.

  • Name
    GET /api/vehicles/no-data-report
    Description

    Vehicles with no telemetry in window.

All daily summary

curl "$LIVEPIN_API_BASE_URL/api/vehicles/all-daily-summary-report" \
  -H "Authorization: Bearer $JWT_TOKEN"

Activity duration reports

  • Name
    GET /api/vehicles/reports/moving-hours-report
    Description

    Moving duration per vehicle per day.

  • Name
    GET /api/vehicles/reports/engine-on-hours-report
    Description

    Engine on duration per vehicle per day.

  • Name
    GET /api/vehicles/reports/stopped-hours-report
    Description

    Stopped duration per vehicle per day.

  • Name
    GET /api/vehicles/reports/idle-hours-report
    Description

    Idle duration per vehicle per day.

Moving Hours

GET
/api/vehicles/reports/moving-hours-report
curl "$LIVEPIN_API_BASE_URL/api/vehicles/reports/moving-hours-report" \
  -H "Authorization: Bearer $JWT_TOKEN"

Engine On Hours

GET
/api/vehicles/reports/engine-on-hours-report
curl "$LIVEPIN_API_BASE_URL/api/vehicles/reports/engine-on-hours-report" \
  -H "Authorization: Bearer $JWT_TOKEN"

Stopped Hours

GET
/api/vehicles/reports/stopped-hours-report
curl "$LIVEPIN_API_BASE_URL/api/vehicles/reports/stopped-hours-report" \
  -H "Authorization: Bearer $JWT_TOKEN"

Idle Hours

GET
/api/vehicles/reports/idle-hours-report
curl "$LIVEPIN_API_BASE_URL/api/vehicles/reports/idle-hours-report" \
  -H "Authorization: Bearer $JWT_TOKEN"

Geofence reports

  • Name
    GET /api/vehicles/reports/geo-fence-report
    Description

    Geofence entry/exit events per vehicle.

  • Name
    GET /api/v2/vehicles/reports/geo-fence-report/:vehicleId
    Description

    Geofence report (v2).

Geofence report

GET
/api/vehicles/reports/geo-fence-report
curl "$LIVEPIN_API_BASE_URL/api/vehicles/reports/geo-fence-report" \
  -H "Authorization: Bearer $JWT_TOKEN"

RTT snapshot report

  • Name
    POST /api/vehicles/reports/rtt-snapshot-report
    Description

    RTT snapshot report generation with trip details and map visualization.

RTT Snapshot

POST
/api/vehicles/reports/rtt-snapshot-report
curl --location "$LIVEPIN_API_BASE_URL/api/vehicles/reports/rtt-snapshot-report" \
  --header "Content-Type: application/json" \
  --header "Authorization: Bearer $JWT_TOKEN" \
  --data '{
    "fromDate": "2026-01-29",
    "fromTimeStamp": "19:45",
    "toDate": "2026-01-29",
    "toTimeStamp": "21:31",
    "tripId": "392771",
    "imeiNumber": "",
    "vehicleNumber": "DUMMY-VEHICLE-301"
  }'

Only one of imeiNumber or vehicleNumber should be sent. Optional fields: mobileNumber, applicationId, isGPSInstalled, isMobileTracked.

Some fleet reports return large payloads or files. For heavy exports, run these requests from backend jobs instead of user-facing request/response cycles.

Drivers and groups

  • Name
    POST /api/drivers
    Description
    Create driver profile.
  • Name
    GET /api/drivers
    Description
    List drivers.
  • Name
    PUT /api/drivers/:id
    Description
    Update driver profile.
  • Name
    DELETE /api/drivers/:id
    Description
    Delete driver profile.
  • Name
    POST /api/vehicle-groups
    Description
    Create vehicle group.
  • Name
    GET /api/vehicle-groups
    Description
    List vehicle groups.
  • Name
    GET /api/vehicle-groups/:id
    Description
    Get one vehicle group.
  • Name
    PUT /api/vehicle-groups/:id
    Description
    Update vehicle group.
  • Name
    DELETE /api/vehicle-groups/:id
    Description

    Delete vehicle group.

Geofence and alerts

  • Name
    POST /api/geofences
    Description
    Create geofence.
  • Name
    GET /api/geofences
    Description
    List geofences.
  • Name
    DELETE /api/geofences/:id
    Description
    Delete geofence.
  • Name
    GET /api/devices/reverse-geocode
    Description
    Reverse geofencing/address lookup.
  • Name
    POST /api/notifications/update-fcm-token
    Description
    Register FCM token.
  • Name
    GET /api/notifications/types
    Description
    List notification event types.
  • Name
    GET /api/notifications/vehicle-notifications/:vehicleId
    Description
    Vehicle notifications stream/list.
  • Name
    POST /api/notifications/update-preferences/:vehicleId
    Description
    Update notification preferences.
  • Name
    GET /api/notifications/vehicle-preferences/:vehicleId
    Description
    Read notification preferences.
  • Name
    POST /api/notifications/send-test-notification
    Description
    Send test push notification.

Create geofence

curl -X POST "$LIVEPIN_API_BASE_URL/api/geofences" \
  -H "Authorization: Bearer $JWT_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"name":"Warehouse","coordinates":[[80.1,13.2],[80.2,13.2],[80.2,13.3]]}'

Get reverse geocode

curl -G "$LIVEPIN_API_BASE_URL/api/devices/reverse-geocode" \
  -H "Authorization: Bearer $JWT_TOKEN" \
  -d latitude=22.64044 \
  -d longitude=88.4169131

Preferences

  • Name
    GET /api/user-preferences/me
    Description

    Read logged-in user preferences.

  • Name
    PUT /api/user-preferences/me
    Description

    Update user preferences.

  • Name
    PUT /api/global-config
    Description

    Update SMS/FCM global config.

Was this page helpful?