API Data Does Not Match Platform Data

The data returned by an API may appear different from the data displayed on the platform when the API request parameters are not provided in the expected format.

For the Fuel CAN Consumption API, the time parameters must be provided in 24-hour format. Using a 12-hour format such as 11:59:59 PM may cause the requested time range to be interpreted incorrectly and result in different API values.

Example Questions

• Why does the API data not match the platform data?
• Why is the Fuel CAN Consumption API showing different values?
• Why is the API returning incorrect Fuel Consumed or Distance values?
• Does the API return the same data as the platform?
• What date and time format should be used in the Fuel CAN Consumption API?
• Why does changing the end time affect the API result?
• Why are the API and platform reports showing different values?

Symptoms / How to Identify

The issue may be identified when:

• API results do not match the corresponding platform report.
• Fuel Consumed values appear different.
• Distance values appear different.
• The API request uses a 12-hour time format such as 11:59:59 PM.
• The API request does not cover the same date/time range as the platform report.

Information Required Before Troubleshooting

Check the following:

• API endpoint being used.
• Vehicle/IMEI number.
• Project ID.
• Start date and time.
• End date and time.
• API response.
• Corresponding platform report data.
• Date and time format used in the API request.
• API authentication/token details, if required.

Troubleshooting Steps

1. Identify the API being used and compare it with the corresponding platform report.
2. Verify that the same vehicle/IMEI is selected in both the API request and platform report.
3. Verify that the start and end date/time are exactly the same in both requests.
4. Check the time format used in the API request.
5. For the Fuel CAN Consumption API, ensure that the time is provided in 24-hour format. Incorrect:
   13-08-2026 11:59:59 PM Correct:
   13-08-2026 23:59:59
6. Submit the API request again with the corrected time format.
7. Compare the API response with the corresponding platform data.
8. Specifically verify values such as:
   • Fuel Consumed
   • Distance
9. If the values still do not match after using the correct date/time format, test the same API request for another vehicle to determine whether the issue is vehicle-specific or API-wide.

Possible Cause

The most common cause in this case is an incorrect time format or time range in the API request.

For the Fuel CAN Consumption API, the time parameters are expected in 24-hour format. An incorrectly formatted end time can cause the API to interpret the requested period differently from the period selected on the platform.

Other possible causes include:

• Different vehicle/IMEI selected.
• Different start/end date or time.
• Different report/API calculation parameters.
• Incorrect API request parameters.
• Vehicle-specific data availability.

Resolution / Action

Use the correct 24-hour time format when sending date/time parameters to the Fuel CAN Consumption API.

For example:

Start: 12-08-2026 12:00:00 End:   13-08-2026 23:59:59

After correcting the request, compare the API response with the platform data using the same vehicle and same time range.

If Fuel Consumed and Distance still differ after validating the request parameters, test another vehicle and share the API request/response with the technical support team for further investigation.