We’re at REST API age, but as Mikrotik users, we only have the fetch tool. And to make us unhappy, the wiki help page of the command doesn’t reflect any change from 2014.
Anybody on earth is sure if http-data needs “payload={}” when using http-method=put ?
And how to send a different content-type header?
Here my first petition: Please, can anybody update the help page with new options and use samples?
And here my second petition to mikrotik developers: Forget fetch command, and implement a curl wrapper.
I don’t understand your reply, I think he has his reasons why he cannot use APIs and build his own comm tool (active side MT → passive side server I guess, same as I have I bet). He is right that /tool fetch is a nightmare. I have been on it 3 years and I still don’t feel fully comfortable whenever I have to try out new things… Documenting this function as much as possible (see my recent certificate post) would be a necessary thing as many people are making use of it.
I can’t understand this answer. Isn’t the same maintain an external system pooling several routers via API, than let routers inform about its state to the external system. We’re speaking about let router use an external API. Inform about its state, etc…
Could be that /tool fetch has some capabilities that I can’t discover, but still is a low-functionality tool. How can I set a custom HTTP header? How can I do it with a PUT verb? Why a new developer needs to understand a new tool while there is a “de facto standard”?