Skip to content
English
Customer portal
www.uffizio.com
  • There are no suggestions because the search field is empty.

Live Data API Returns “Data Not Found”

When using the Live Data API, the access token may be generated successfully, but the getTokenBaseLiveData API can return “Data Not Found” if the API request, project configuration, user access, company assignment, or requested vehicle/company data does not match the required configuration.

Example Questions

    • Why does getTokenBaseLiveData return “Data Not Found”?
    • The access token is generated successfully, but why is Live Data not returned?
    • What Project ID should be used for the Live Data API?
    • Can Company-wise Live Data be retrieved using a Company User or Company Subuser?
    • Why is Live Data not returned for a specific company or vehicle?

Symptoms

The access-token API works successfully, but the Live Data API returns a response similar to:

{   "result": 0,   "message": "Error in Service : Data Not Found !" }

Information Required

Before troubleshooting, collect:

  • API username/account being used.
  • Company name.
  • IMEI or vehicle name, if requesting vehicle-specific data.
  • Project ID.
  • API request URL.
  • Request headers.
  • Request body.
  • API response.
  • Screenshot of the API parameters and configuration.

Troubleshooting Steps

1. Verify the Project ID

Confirm that the API request uses the correct Project ID associated with the tracking project.

For example, the Project ID mentioned for the Trac-Pro Premium project is 37.

2. Verify API User Type

If using the Company-wise Live Data API, the API credentials should belong to the relevant Company User or Company Subuser.

When the Company-wise API is used without specifying an IMEI or vehicle name, the API returns Live Data for vehicles accessible to that company/user.

3. Verify Project Access

Check that the API user has access to the required project.

If the user has access to more than one project, the Live Data API may not work as expected. Verify that the API user is associated with the correct project.

4. Verify Company Assignment

Confirm that the company being requested is assigned to the API user.

If using Company-wise Live Data, verify that the company name in the request exactly matches the company configured in the platform.

Example:

{     "company_names": "TRAC-PRO",     "format": "json" }

5. Verify Live Data API Access

Confirm that getTokenBaseLiveData is enabled and available for the account.

6. Verify Vehicle/IMEI Data

If requesting data for a specific vehicle, verify that:

  • The IMEI is correct.
  • The vehicle belongs to the requested company.
  • The vehicle is accessible to the API user.
  • The device is communicating with the platform.
  • Live data is available during the API request.

Possible Causes

  • Incorrect Project ID.
  • API user does not have access to the required project.
  • API user is associated with an incorrect company.
  • Incorrect company name in the request.
  • Vehicle/IMEI does not belong to the requested company.
  • API user does not have access to the requested vehicle.
  • getTokenBaseLiveData is not enabled for the account.
  • No live data is available for the requested vehicle/company at the time of the API request.
  • Incorrect API parameters, headers, or request body.

Resolution

Verify the Project ID, API user type, project access, company assignment, API permissions, and vehicle/IMEI details before testing the Live Data API again.

For Company-wise Live Data, ensure that the company name is correctly passed in the request body and that the API user has access to that company.

If the issue continues, share the API URL, parameters, headers, request body, API response, API username, company name, and IMEI/vehicle details with the support team for further investigation.