RMS API — POST /devices/connect returns HTTP 404

Networking Solutions Discussion
1

Subject: RMS API — POST /devices/connect returns HTTP 404

We are developing a Windows application that generates RMS Connect links for third-party LAN devices connected through a RUT241.

Authentication succeeds with a Personal Access Token containing:

devices:read
device_remote_access:read
device_remote_access:write

The API successfully:

  • Finds the RUT241 using its serial number.
  • Returns the HTTP Remote Access entry for the DVR at 192.168.1.64:80.
  • Returns Remote Access ID 4174603.

However, this request:

POST https://api.rms.teltonika-networks.com/devices/connect?access_id=4174603

with body:



{
  "duration": 3600
}

returns:



HTTP 404 Not Found
Resource not found

The same Remote Access entry works correctly when opened manually through the RMS web interface.

Could you confirm:

  1. The current API endpoint for starting an RMS Connect session.
  2. Whether access_id should be passed in the query string or request body.
  3. Whether another scope is required.
  4. Whether session creation through the API is currently supported for HTTP access to third-party LAN devices.