Issue in Reports API with Admin Session

Rishi 6 days ago

Hi All,

We are currently using Traccar 6.5 and have noticed a difference compared to our production setup, which is on Traccar 4.10.

When we call the Trips or Routes API using an admin session with device IDs that belong to other users, we no longer receive any data in the new version. In the older version, the same request returned data without any issues.

Could you please let us know if there were any permission or scope changes introduced in Traccar 6.x that affect admin access to route or trip reports?

Thanks for your help.

Anton Tananaev 6 days ago

There were a lot of changes in 6.x. You should read release blog posts.

Rishi 6 days ago

Hi,

Thank you for the prompt response, and I have found this in the release notes for version 5.2 where it is mentioned like >Token API authentication - token can now be used directly for all API calls`

Does this effect the ability for admin session to take reports for user devices?

Anton Tananaev 6 days ago

No, why would it affect any functionality?

Rishi 3 days ago

Hi,

Thanks for the clarification. I agree that token authentication itself should not change functionality.

To explain our case more clearly:

In Traccar 4.10, when we logged in as admin, we were able to call the report APIs (e.g. trips, summary, events) with any user’s deviceId and receive data, even if the admin user was not explicitly linked to those devices.

After upgrading to 6.x, using the same logic, the APIs now return an empty array unless the admin user is explicitly assigned to those devices.

Could you please confirm if, after 4.10, there was a change where report queries are filtered strictly by the authenticated user’s device permissions (even for admin users)?

If so, is there a recommended way for an admin to generate reports across all users’ devices without manually linking every device to the admin account?

Thank you for your time.

Anton Tananaev 3 days ago

You have to link devices to be able to generate reports.

Rishi 3 days ago

Ok, Thank you very much for the clarification.