Could you confirm if these APIs are still in beta or if they have been released for production use? Additionally, could someone provide the complete URL path necessary to execute the API calls from the link above?
I have successfully used the basic APIs listed here without any issues:
From what I’ve gathered, you’re trying to create a new SMS rule using the aforementioned API call. I can see that the developers portal you have open is for the FW version 7.6, is that what you’re using on your RUT955 as well? If so, would it be possible for you to try and upgrade your firmware to the latest available version?
To answer your question regarding if these are BETA or not, I believe they still are as there’s still the “BETA” indicator that can be seen in the corner, though we’ve had multiple clients successfully using these in production, so you shouldn’t really have any issues with that.
Finally, what kind of responses are you getting when attempting to push the config?
Current version: RUT9_R_00.07.06.12
Last available: RUT9_R_00.07.06.17
From the link here I can not find version 7.6 which introduces the API calls I want:
This is what I get when I execute this script:
#!/bin/bash
# Read token from file
TOKEN=$(cat PAT.txt)
# Teltonika API URL
API_URL="https://rms.teltonika-networks.com/api/devices/1227829/sms_utilities/rules/config"
# Send HTTP GET request with the token
curl -X GET "$API_URL" \
-H "Authorization: Bearer $TOKEN" \
-H "Content-Type: application/json" \
-o response.json # Save response to a file
echo "Response saved to response.json"
If you are on 7.6.17, then there’s nothing to worry about, it is the latest available version for your device. Regarding the developers portal, you should probably use this link (although there might not be any difference, at least I haven’t noticed any): https://developers.teltonika-networks.com/reference/rut955/7.6.17/v1/sms-utilities
Regarding your script that you’re trying to run, from what I’m able to tell, you’re trying to retrieve the current configuration of the available SMS commands, not create a new one, is that what you’re trying to achieve?
I’ll contact our R&D to ask more about this as they might know more, because regarding the response you get, apparently the option does not even exist. Authorization doesn’t seem to be the issue here as you mentioned other calls work just fine.
Authorization is OK because I store my access token in PAT.txt file.
You are right, I am trying to read SMS rules, just for the test because any other command from the ling I have provided is not working.
Like I said, I am not on 7.6.17 but on 7.06.12. and the latest version that is available for download is 7.06.17.
Is 7.06.17 actually 7.6.17?
Sorry, looked at the wrong side of your screenshot, 7.06.17 and 7.6.17 are the same versions, I’m just skipping writing the zero for convenience’s sake. You can update to the latest version and try again if that doesn’t work - kindly wait for a response from me whenever our R&D answers my query.
“The client seems to be using an RMS API call endpoint, that doesn’t exist. You can check available RMS API endpoints here: API Reference | Developers. Instead, for getting SMS rules configuration he should use the endpoint from the page you’ve provided here. Even though the API developers portal is still presented as BETA, the specified API endpoints work as intended.”
Regarding the scope of APIs, this is sort of answered in the reply that I’ve got. RMS doesn’t have some (or even most) of these calls, only those you see in the developer.rms portal. The ones that you are trying to use (eg.: SMS utilities) are separate.
So to use sms_utilities API endpoint I need to be in the same network as RUT955 since there is the IP address specified in the URL provided in your answer above, and there is not other way to use them remotely? For that I don’t need any access tokens?
As seen in the developer.rms portal, “sms_utilities” is not present in the scope, that, I believe, is intended to be the case. As mentioned earlier, if you want to set up SMS utilities using API calls, you’ll have to refer to the Developers portal.
