RUT200 Web API needs

I am developing solution that uses RUT200 devices. And I need the following:

API to get the SSID & WIFI password of the device.

And pointers appreciated,

Steven

Have a look at api GET /wireless/interfaces/config or its subsidiary call api GET /wireless/interfaces/config/{id}

The link references Teltonika’s Network API documentation. Note that you have to select both your Model and Firmware version, for the correct documentation.

Thanks Mike - great help.
Could you also direct me to how to read and set the RUT200 failover feature. I understand from Teltonika support that it is OFF by default. Eg - if there is internet upstream from the WAN port it does not take precedence over the 4G/5G connection - unless failover is enabled.
If my understanding is correct - I am looking for the API to cleanly read the failover state and set it either on / off.
Best Regards
Steven

Greetings, @sb-kleenhub ,

Welcome to the Teltonika Community!

As @Mike mentioned, you can use API calls to check the status of the failover feature as well as apply configuration changes programmatically.

You can find the API documentation here:

Please make sure to select your specific device model and firmware version in the documentation. Then, you can use the search field at the top of the page and type Failover to display all available API endpoints related to this functionality.

For example:

  • PUT /failover/interfaces/config – allows you to modify the failover configuration.
  • GET /failover/interfaces/config – returns the current failover configuration and status.

Using these endpoints, you should be able to both monitor the failover state and adjust its configuration as needed.

Please let me know if you require any additional assistance.

Best regards,
V.

Hi Again,

I am also trying to read / set the APN through the API. But I am a little confused. When I try to GET it from a RUT200 where I have set it manually it does not return that APN - but only the rest on the list:

pi@khpi-f05a38:~ $ curl -skS https://192.168.1.1/api/modems/apns/status \
  -H "Authorization: Bearer 4b47df7f81a83ba582c9f9e72d439079" \
  -H 'Accept: application/json' | jq
{
  "success": true,
  "data": [
    {
      "apns": [
        {
          "password": "",
          "apn": "internet",
          "user": "",
          "id": 53,
          "carrier": "T-Mobile",
          "pdptype": "0",
          "auth": "none"
        },
        {
          "password": "",
          "apn": "internet.ben",
          "user": "",
          "id": 55,
          "carrier": "T-Mobile",
          "pdptype": "0",
          "auth": "none"
        },
        {
          "password": "",
          "apn": "basic.internet.ben.data",
          "user": "",
          "id": 56,
          "carrier": "T-Mobile",
          "pdptype": "0",
          "auth": "none"
        }
      ],
      "modem": "1-1"
    }
  ]
}

Greetings, @sb-kleenhub ,

I hope you’re doing well,

What you are seeing is the expected behaviour of the /api/modems/apns/status endpoint. This endpoint queries the APN database - a pre-loaded list of carrier APNs that the device uses for its Auto APN feature - rather than the active APN configuration of your mobile interface. Because of this, it will return carrier-matched entries (in your case, T-Mobile’s pre-loaded APNs) but will not reflect the APN you have manually set on the interface itself.

To read and set the APN that is actually in use by the mobile connection, you need to interact with the network interface configuration endpoints instead. Specifically:

• GET /api/interfaces/config - returns the current configuration of all interfaces, including the active APN set on your mobile interface.
• PUT /api/interfaces/config/{id} - allows you to update the configuration, including changing the APN, disabling Auto APN, and setting credentials.

Please make sure you are referencing the documentation for your specific device model and firmware version at:

As endpoint paths and available parameters can vary.

A couple of additional tips:
• If Auto APN is still enabled on the interface, the manually set APN may be overridden. You will want to ensure Auto APN is toggled off when setting a custom APN via the API.
• For further context on how Auto APN works and its interaction with manually configured APNs, the Teltonika Wiki article is a helpful reference.

Please let us know if you run into any issues or need help identifying the correct interface ID for your device - happy to assist further.

Best regards,
V.

Hi,

Thanks for the information. I have implemented support for managing the APN through my application and it works great.

I next added support to allow me to manage the SW upgrade, so I am using /firmware/device/status to get the current version installed so I can view it in my dashboard across installed device.

I can see that there is quite a few methods related to triggering a remote SW update, ideally from your server. Can you advice on what methods to use and what is required to track progress.

Is “fota” Firmware Over The Air?

Best regards

Steven Boye