Bulk DG800 Serial Number Lookup
Merge DC400 and DG800 Events
Service Ticket Parser
DG800 Odometer Data Lookup
VIN Parser
If both CSV and pasted VINs are provided, CSV takes priority.
DC400 Review
Select DC400 Events (max 2)
Camera Uptime Report
Camera Serial Numbers (comma or space separated):
Select up to 2 Events (Monthly Counts)
You may select up to two DC400 events. Counts will be added per month.
Engine Performance Report
Asset Location IntelliShift
JSON to CSV Timezone Converter
or drag and drop your file here
| Filename | UTC Time | Selected TZ Time |
|---|
Showing first 100 entries
Jira Ticket Status
JSON Comparison Matrix Generator
Config Set Comparison Matrix
Authenticate DC300
This will authenticate and fetch the DC300 maintenance URL.
Install Verification Test change
GeoSensorX Config Adjustments
DG800 Devices
DC400 Devices
Config Definition Generator
Upload a CSV exported from the Excel configuration table. This will generate DG800 and DC400 config definition arrays.
DG800 Config Output
DC400 Config Output
Kore DG800 Plan Update
Video Events Report
Bulk DG800 Serial Number Lookup
GPS Lost / Acquired Review
Extract Inspections Details
Upload Driving Behavior CSV
Select a CSV file containing harsh event metrics. It will classify each vehicle as Light, Medium, or Heavy duty.
Hardware / Camera Inventory Merge
Uses files from /uploads:
Hardware.xlsx, Camera.xlsx,
dc400.csv, gsx_800.csv (CSV integration coming next).
IntelliShift Tools
All calls share the same pattern: load data ➜ select item ➜ view/edit ➜ call API ➜ export CSV.
🔐 Authentication
🚗 Assets & Vehicles
Vehicle Patch (Legacy / Vehicles API)
Assets (List, View, Update, Create)
Create New Asset (POST /assets)
Current Asset Locations
Fetches current locations from /api/assets/current-locations and exports JSON to CSV.
Historical Asset Location Search
POST /api/intellishift/assets/search-locations
Vehicle Location History (asset-locations/vehicles)
GET /api/intellishift/asset-locations/vehicles
🏢 Branches
Branches (List, View, Update, Create, Assign Vehicles)
Create New Branch (POST /branches)
Assign Vehicles to Selected Branch
Body example: { "vehicleIds": [101, 102] }
👤 Operators & HOS Logs
Operators (List, View, Update, Create)
Create New Operator (POST /operators)
Operator Logs & Entries
🧰 Issues & Maintenance
Issues (List, View, Create, Update, Status, Comments)
Create New Issue (POST /issues)
Set Issue Status
Body example: { "status": "Closed" }
Add Comment
Body example: { "text": "Comment text" }
📡 Data & Telemetry
Data Points & Codes
Driver Identifier Devices
Create New Driver Device
Assign Device to Selected Operator
Body example: { "operatorId": 500 }.
If you've loaded operators and selected one, the JS can auto-fill this.
✅ Inspections
Inspections & Components
📍 Landmarks
Landmarks (List, View, Update, Create, Delete)
Update Selected Landmark (PUT)
Create New Landmark (POST)
Delete Selected Landmark
Landmark Geofence Alert Logs
🛑 Geofences
Geofences (List, View, Update, Create, Delete)
Update Selected Geofence (PUT)
Create New Geofence (POST)
Delete Selected Geofence
Geofence GeoJSON
🏷️ Tags
Tags (List, View, Update, Create, Delete)
Update Selected Tag (PUT)
Create New Tag (POST)
Delete Selected Tag
Assign Assets to Tag
Assign Operators to Tag
IntelliShift Log Troubleshooting
End-to-end workflow:
Load operators & assets → select operator & date → fetch logs → choose entries →
auto-join with trips, assets, hardware CSV, & DG800 history → export CSV.
Step 0 – Customer & Inventory Mapping
We automatically load your hardware inventory from the /uploads directory.
The customer location helps match assets → serial → IMEI.
Step 1 – Load Operators & Assets
Step 2 – Select Operator & Date Range
Step 3 – Select Log Entries
Select one or more entries below. For each entry, the system will:
• Fetch trips for the log
• Match trips by timestamp
• Join asset details + inventory serial/IMEI
• Fetch DG800 historical events near the timestamp
| Select | Entry ID | Log ID | Timestamp | Status | Type | Origin | Event Code | Geolocation |
|---|
Trips Match Preview
| Entry Timestamp | Trip Start | Trip End | Asset ID | Asset Name |
|---|
Inventory Match Preview
| Asset Name | Inventory Location | Serial Number | IMEI |
|---|
DG800 Historical Range
DG800 Event Preview
| Serial | Server Timestamp | Device Timestamp | Vehicle Batt | GPS Speed | Event Name | Matched Entry Timestamp | Matched Entry ID |
|---|
Step 4 – Export Joined CSV
Debug Log (Click to Expand)
IntelliShift Landmark Import
Use this tool to import landmarks into IntelliShift from a CSV or Excel file. We’ll automatically:
- Use your saved IntelliShift token/credentials.
- Read landmarks from your CSV/XLSX.
- Look up landmark categories, creating any missing ones.
- Match branches by ID or name.
- Round the requested radius in feet up to the nearest available Radius ID.
- Post each landmark to the
POST /api/landmarksendpoint. - Return a CSV report with a status per row.
Template Rules (summary)
- LocationName is required – this becomes the landmark name.
- Provide either Street + Zip or Latitude + Longitude.
- You may include CategoryID or a CategoryName. If a name doesn’t exist, it will be created.
- RadiusFeet (or “Radius in feet”) is optional – we round up to the closest allowed radius.
- SubgroupID or BranchName is optional – we match against the Branch list.
- AccountNo, TankNo, and Notes are optional.
Step 1 – Template & File
Step 2 – Import Landmarks
When you click Start Import we will:
- Validate your IntelliShift token (or re-authenticate).
- Load Categories and Branches from IntelliShift.
- For each row in your file:
- Resolve or create the Category.
- Resolve the Branch (SubgroupID) by ID or name.
- Compute the correct RadiusId from the radius in feet.
- Call
POST /api/landmarks.
Step 3 – Results CSV
After the import completes you can download a CSV summarizing what happened for each row (success, error, created categories, matched branch, etc.).
IntelliShift Asset Import
Use this tool to add or update Assets (Vehicles) in IntelliShift from a CSV or Excel file. The system will:
- Use your saved IntelliShift token/credentials.
- Load all existing Assets and Branches to match updates.
- Match Asset Name, VIN, or externalAssetId to detect update vs create.
- Resolve Branch names → Branch IDs automatically.
- POST new Assets to
/api/intellishift/assets/vehicles. - PUT existing Assets using
/api/intellishift/vehicles/{id}. - Return a CSV report with the result of every row.
Template Rules
- assetName (or name) is required.
- vin is optional but strongly recommended for matching.
- branchName (or branchId) is optional; branchName will be mapped.
- year, makeId, modelId, and trimId are optional.
- engineHours and odometer are optional.
- isActive defaults to true if omitted.
Step 1 – Template & File
Step 2 – Import Assets
When you click Start Import, the system will:
- Validate IntelliShift authentication.
- Download all Assets and Branches.
- Match rows by VIN, externalAssetId, or assetName.
- Resolve Branch ↔ BranchId.
- POST or PUT each asset.
Step 3 – Results CSV
After the import completes, download a CSV summarizing the actions taken.
IntelliShift Operator Import
Use this tool to add or update Operators in IntelliShift from a CSV or Excel file. The system will:
- Use your saved IntelliShift token/credentials.
- Load all existing Operators and Branches to match updates.
- Match Branch names → Branch IDs automatically.
- POST new Operators to
/api/operators. - PUT existing Operators using
/api/operators/{id}. - Return a CSV report with the result of every row.
Template Rules
- operatorName is required.
- firstName and lastName are optional.
- branchName (or BranchId) is optional; branchName will be mapped.
- medicalCardExpiration must be in a parsable date format.
- pin is optional.
- externalReferenceId is optional.
Step 1 – Template & File
Step 2 – Import Operators
When you click Start Import, the system will:
- Validate IntelliShift authentication.
- Download all Operators and Branches.
- Match rows by operatorName or externalReferenceId to detect update vs create.
- Resolve Branch ↔ BranchId.
- POST or PUT each operator.
Step 3 – Results CSV
After the import completes, download a CSV summarizing the actions taken.
Hardware Inventory Lookup
Paste device_name + timestamp rows below: