Teltonika RMS API 403 on device task execution

Hello,
I have a problem with Teltonika RMS API.
So, I have a token generated with these access scopes:

devices:read
device_tasks:read
device_tasks:write
device_task_groups:read
device_task_groups:write

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:

{
    "success": false,
    "errors": [
        {
            "code": "FORBIDDEN",
            "message": "Forbidden."
        }
    ]
}

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.

What could be causing this?

Hello,

I have just tested this function, and everything works as expected.

A “Forbidden” response might occur if, when creating a token, you did not select the Device Tasks scopes to be accessible using that token.

Please ensure that you have selected these scopes, and let me know how it goes!

Best regards,

Hi Marija,

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 have sent you a form to fill out. Once completed, I will contact you privately regarding this issue.

For the Ticket ID, please use “10552”.

Best regards,

Hello,

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.

Thank you for your patience and understanding.

Best regards,

Hi Marija,
It seems to be working fine already.

Hello,

Yes, the issue has been resolved.

Please let me know if you have any further questions or need additional assistance.

Best regards,

This topic was automatically closed after 60 days. New replies are no longer allowed.