Thanks, specifiing .id in /print does not seem to work (i'll get argument error), at least not in beta9, however since I am more interested in getting all the fields of all the records (like getall), it is still almost exactly what I need.
Only thing I am missing in what /print +detail shows, are the flags (getall has those, but is missing some other things here).
But if I'll need them, I could combine all together.
my bad, to launch command that will be tagged you issue:
and after that if you want to cancel that command you are runnning:
also you can provide /cancel with its own id:
to combine results you can use objects that contains all the fields you need (at least, this is what i am doing)
about connecting to api port:
first you need to enable api on the router:
and then you can connect to default api port 8278
and please specify what programming language you are using to connect and what problems you encounter.
also, you can run sniffer on the router so you can see your progress of the connection (like what is router sending what is your client program sending) as you can see actual contents of the packet (like commands sent to router, what is router response if there is response in the first place)