RouterOS API: for those who don't REST

Application Programmable Interface (API) allows users to create custom software solutions to communicate with RouterOS to gather information, adjust the configuration, and manage the router. You can save loads of time with API - Druvis will teach you how!

[hexa.officially]

Thanks for that valuable video.
Please we need libraries to be developed and coded by your engineers, imagine having a library for C# then a huge number of interfaces will come to be publicly available for people to develope varies tools, create a concept that community can add value to it please.

[FinlayDaGk]

Honestly, I like the REST API more.
Sure it may be less efficient on paper but it's simplicity very well makes up for it imo.

[oliver]

I'm confused, does this API work on RouterOS v6 and the REST API is only RouterOS v7?

[martinmadsen]

Plan to make the socket bi-directional? Would love to see MT push 802.11v to an upstream of my choosing. While at it, would you consider letting us fill the 802.11k lists via API?

Seems like such a lost opportunity when the hardware (hAP AC2 etc) supports the standard, but we all seem to be stuck waiting for MT build a controller.

[danielbaraza]

Some commands aren’t producing any results despite them working on the command line. For example this command does nothing. ppp secret disable [find name=user] how can you execute this command with python mikrotik api?

[wreckedzilla]

Great content, will try it out. MT Courses for automation engineers? :)

[nikolaydachev]

ansible have routeros api modules which make the live more easy .. also for python librouteros is a superior :)

[christianmorgan]

The documentation is just as bad as the community forums, please update your documentation with proper examples Mikrotik.

[jonathanhirschbaum]

REST is there for a reason. I wish you all luck in rewriting global established standards but I would appreciate if you stop