OEM API Notifications

Format and standards for API Failure Notifications

Overview

Data accuracy is critical when synchronizing data with Original Equipment Manufacturers (OEMs). To ensure billing and reporting remain accurate, Prestartr monitors all API data exchanges.

If a data push or pull fails, the system automatically sends an email notification to the designated System Administrator. 

This allows your team to investigate the error, adjust data sources, and verify critical fields immediately.


Supported Providers

Prestartr supports automatic failure notifications for the following integrations:

Bell

Kobelco

Verizon

Geotab

Komtrax

VisionLink

Helix

SmartFill

Volvo

Hitachi

Teletrac Navman

 

John Deere

Toyota  

Setting Up Notifications

You can configure notifications to go to specific users for specific integrations, or assign a user to receive alerts for all providers.

Navigate to the Catalogues module.

Select the OEM Email Notification submenu.

Assign Users to integrations:

Global Alerts: Use the All menu to notify a user about all failure events regardless of the provider.

Specific Alerts: Select specific users for individual integrations (e.g., assign the Fleet Manager to "Toyota" and the IT Admin to "Verizon").

Click Save to confirm your changes.


Notification Details

When a failure occurs, the assigned user will receive an email containing a summary of the issue and a detailed attachment.

Email Format

Subject: <OEM Provider> <Run Date/Time> <Success or Failure>

Body: Lists the Plant ID and the Failure Type.

Attachment Details

A file attached to the email will provide a detailed breakdown to assist with troubleshooting:

  • OEM Name
  • Run Date/Time
  • Status (Success/Failure)
  • Plant ID
  • Odometer Reading
  • GPS Coordinates (Lat/Long)
  • Fuel Level
  • Specific Error Reason

Common Failure Triggers

The system will generate a notification if any of the following errors occur during an API sync:

API Connectivity Failure: The system could not connect to the provider's server.

Telematics ID Not Found: The unique identifier for the machine does not match the provider's records.

Odometer Reading Failure: The system could not retrieve valid usage hours or mileage.

GPS Location Failure: The system could not retrieve valid coordinates.