![]() ![]() We will also provide documentation as the intended goal is for it to be used by the public. It is meant to be public and REST-like (opens new window). Not an evolution of the current one, but 100% new. This led us to add more tooling around it, like xo-cli and to answer specific requests.įor these reasons we decided to build a new API. The REST API allows you to automatically connect clients and systems to your monitoring tool using simple HTTP calls. They allow clients to use your monitoring tools and resources without allowing access to your backend, say, server database. This is perfect for our usage, but a bit complicated for others.Īlso, this API wasn't meant to be public, but over the years some users have expressed a desire to be able to use it for their own purposes. The resource URL, headers and body (which is called payload) can include additional request parameters and data. In the context of network monitoring, REST APIs are digital middlemen who handle requests and responses. That's why it's a JSON-RPC API connected via websockets, allowing us to update objects live in the browser. Launch requests on the different network. ![]() We originally developed our existing API to be used between the Web UI xo-web and the server backend, xo-server. API tests help you proactively monitor your most important services so they are available anytime and from anywhere. This page is only here to explain how it works, it's not intended to be used as an accurate guide. Since 1997, we offer monitoring solutions for businesses across all industries and all sizes, from SMB to large enterprises. The fully up-to-date README is available here (opens new window). Representational State Transfer (REST) is a software architecture that imposes conditions on how an API should work. This is a beta feature that may see some changes in the future. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |