Difference between revisions of "RMS API"
m (Protected "RMS API" ([Edit=Allow only administrators] (indefinite) [Move=Allow only administrators] (indefinite))) |
|||
| (5 intermediate revisions by 2 users not shown) | |||
| Line 4: | Line 4: | ||
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! | 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 | + | The main RMS API is a [https://en.wikipedia.org/wiki/Representational_state_transfer RESTful] 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. |
[[File:Exciting-rms-news-connect-and-api-3.png]] | [[File:Exciting-rms-news-connect-and-api-3.png]] | ||
==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]] | ||
| + | Helpe me. Please | ||
Revision as of 11:30, 27 January 2022
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 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. Helpe me. Please
