RMS API: Difference between revisions
No edit summary |
No edit summary |
||
Line 9: | Line 9: | ||
==Documentation== | ==Documentation== | ||
For the RMS API documentation, we have a separate Wiki page: [https://developers.rms.teltonika-networks.com/ Developers.rms.teltonika-networks.com] | For the RMS API documentation, we have a separate Wiki page: | ||
* [https://developers.rms.teltonika-networks.com/ Developers.rms.teltonika-networks.com] | |||
Here you will find all the necessary information to start working with RMS API. | |||
[[Category:RMS]] | [[Category:RMS]] |
Revision as of 11:58, 23 September 2021
Main Page > IoT Platforms > RMS > RMS APISummary
RMS API – provides a possibility to carry endless RMS features into your in-house IoT platform, in case you would rather stick to your familiar interface. That is probably the biggest beauty of the RMS – you can use whatever you like and leave the rest. It adapts to your particular business needs and your environment. Starting with a user interface, varying methods to reach devices or selecting features, and ending with a pricing model that works best in your business case – you are in control to choose all of it!
The main RMS API is a RESTful (opens new window)interface, providing programmatic access to much of the data and actions in the system. It provides predictable URLs for accessing resources and uses built-in HTTP features to receive commands and return responses. This makes it easy to communicate with from a wide variety of environments, from command-line utilities to gadgets to the browser URL bar itself.
Documentation
For the RMS API documentation, we have a separate Wiki page:
Here you will find all the necessary information to start working with RMS API.