And I’m using it to retrieve device task groups, tasks and run the device task using these endpoints:
GET https://rms.teltonika-networks.com/api/devices/tasks/groups
GET https://rms.teltonika-networks.com/api/devices/tasks
POST https://rms.teltonika-networks.com/api/devices/tasks/groups/{group_id}
And generally it was working fine until this afternoon when I started to get these responses from the last POST endpoint:
So, I’m still able to get tasks and groups but not execute them.
I thought there might be a change in scopes so I generated a new token with access to every scope, just to test. And the behaviour is still the same. I get 403 with no more details.
Yes, I’ve already selected all five scopes mentioned in my initial post. What’s strange is that they’ve been set this way for at least 2-3 months, and everything was working fine until it suddenly stopped yesterday. I haven’t made any changes.
Even when I generate a new access token with all the scopes selected (using the “select all” checkbox), the response still returns a 403 error.
I wanted to inform you that there are currently some issues with the “Execute Device Task” functionality. Our developers are actively working on resolving these.
As for the get, put, and delete parameters, all of these should be working successfully.
I apologize for any inconvenience this issue may have caused. I will keep you updated with any news regarding when the issue will be resolved.