Manual:API

Summary

Application Programmable Interface (API) allows users to create custom software solutions to communicate with RouterOS to gather information, adjust configuration and manage router. API closely follows syntax from command line interface (CLI). It can be used to create translated or custom configuration tools to aid ease of use running and managing routers with RouterOS.

To use API RouterOS version 3.x or newer is required.

By default API uses port #8728 and service is disabled. More on IP/Services management see in corresponding manual section. Corresponding service name is api

Protocol

Order that has to be closely followed by API client to communicate with RouterOS and receive replies from it.

Description

Communication with router is done by sending sentences to the router and receiving one or more sentences in return. Sentence is sequence of words terminated by zero length word. Word is data that has to be sent to router or part of reply of router encoded in certain way - encoded length and data. Communication happen by sending sentences to the router and receiving replies to sent sentences. Each sentence sent to router using API should contain command as a first word followed by words in no particular order, end of sentence is marked by zero length word. When router receives full sentence (command word, no or more attribute words and zero length word) it is evaluated and executed, then reply is formed and returned.

API words

Words are part of sentence. Each word has to be encoded in certain way - length of the world followed by word content. Length of the word should be given as count of bytes that are going to be sent.

Length of the word is encoded as follows:

Value of length	Number of bytes	Encoding
0 <= len <= 0x7F	1	len, lowest byte
0x80 <= len <= 0x3FFF	2	len | 0x8000, two lower bytes
0x4000 <= len <= 0x1FFFFF	3	len | 0xC00000, three lower bytes
0x200000 <= len <= 0xFFFFFFF	4	len | 0xE0000000
len >= 0x10000000	5	0xF0 and len as four bytes

• Each word is encoded as length, followed by that many bytes of content;
• Words are grouped into sentences. End of sentence is terminated by zero length word;
• Scheme allows encoding of length up to 0x7FFFFFFFFF, only four byte length is supported;
• Bytes of len are sent most significant first (network order);
• If first byte of word is >= 0xF8, then it is a reserved control byte. After receiving unknown control byte API client cannot proceed, because it cannot know how to interpret following bytes;
• Currently control bytes are not used;

Command word

• First word in sentence is called command followed by attribute worlds and zero length word or terminating word.
• Name of command word should begin with '/'.
• Names of commands closely follow CLI, with spaces replaced with '/'. There are commands that are specific to API;

API specific commands:

getall
login

Command word examples:

/login
/ip/address/getall
/user/active/listen
/interface/vlan/remove
/system/reboot

API sentences

API sentence is main object of communication using API.

• Empty sentences are ignored.
• Sentence is processed after receiving zero length word.
• There is a limit on number and size of sentences client can send before it has logged in.
• Sentence structure is as follows:
  • Should contain command word;
  • Should contain zero length word to terminate the sentence;
  • Can contain none or several attribute words. There is no particular order at what attribute words has to be sent in the sentence;
  • Can contain none or several query words. Order of query words in the sentence is important.

Note: Zero length word terminates the sentence. If it is not provided router will not start to evaluate sent words and will consider all the input as part of the same sentence.

• • Next, arguments can be specified. Examples:

=address=10.0.0.1
=name=iu=c3Eeg
=disable-running-check=yes

• • Command argument should begin with '=' followed by name of argument, followed by another '=', followed by value of argument.
  • There are API specific arguments, such as .id. Names of API specific arguments begin with dot.
  • Argument value can be empty and can contain '='.
  • Command sentence can have parameters that are specific to and processed by API protocol. These parameters should begin with '.' followed by name of parameter, followed by '=', followed by value of parameter.
  • Currently the only such parameter is 'tag'.
  • Order of arguments and API parameters is not important and cannot be relied on
  • Commands can have additional query parameters that restrict their scope. They are explained in detail in separate section. Exapmle:

/interface/print
?type=ether
?type=vlan
?#|!

• • Query words begin with '?'.
  • Order of query words is significant.
  • Currently only 'print' command handles query words.
  • First word of reply begins with '!'.
  • Each command generates at least one reply (if connection does not get terminated).
  • Last reply for every command is reply that has first word !done.
  • Errors and exceptional conditions begin with !trap.
  • Data replies begin with !re
  • If API connection is closed, RouterOS sends !fatal with reason as reply and then closes the connection.

Initial login

Template:Apic

Template:Apic

Template:Apis

Template:Apis

Template:Apis

Template:Apic

Template:Apic

Template:Apic

Template:Apic

Template:Apis

Template:Apis

• First, clients sends /login command.
• Note that each command and response ends with an empty word.
• Reply contains =ret=challenge argument.
• Client sends second /login command, with =name=username and =response=response.
• In case of error, reply contains =ret=error message.
• In case of successful login client can start to issue commands.

Tags

• It is possible to run several commands simultaneously, without waiting for previous one to complete. If API client is doing this and needs to differentiate command responses, it can use 'tag' API parameter in command sentences.
• If you include 'tag' parameter with non-empty value in command sentence, then 'tag' parameter with exactly the same value will be included in all responses generated by this command.
• If you do not include 'tag' parameter or it's value is empty, then all responses for this command will not have 'tag' parameter.

Command description

• /cancel
  • optional argument: =tag=tag of command to cancel, without it cancels all running commands
  • does not cancel itself
  • all canceled commands are interruped and in the usual case generate '!trap' and '!done' responses
  • please note that /cancel is separate command and can have it's own unique '.tag' parameter, that is not related to '=tag' argument of this command

• listen
  • listen command is avaliable where console print command is available, but it does not have expected effect everywhere (i.e. may not work)
  • !re sentences are generated as something changes in particular item list
  • when item is deleted or dissapears in any other way, the '!re' sentence includes value '=.dead=yes'
  • This command does not terminate. To terminate it use /cancel command.

• getall
  • getall command is available where console print command is available. Since version 3.21 getall is an alias for print.
  • replies contain =.id=Item internal number property.

• print
  • API print command differs from the console counterpart in the following ways:
    • where argument is not supported. Items can be filtered using query words (see below).
    • .proplist argument is a comma separated list of property names that should be included for the returned items.
      • returned items may have additional properties.
      • order of returned properties is not defined.
      • if list contains duplicate entries, handling of such entries is not defined.
      • if propery is present in .proplist, but absent from the item, then that item does not have this property value (?name will evaluate to false for that item).
      • if .proplist is absent, all properties are included as requested by print command, even those that have slow access time (such as file contents and perfomance counters). Thus use of .proplist is encouraged. Omission of .proplist may have high perfomance penalty if =detail= argument is set.

Queries

print command accepts query words that limit set of returned items. This feature appeared in the 3.21 version.

• Query words begin with '?'.
• Order of query words is significant. Query is evaluated starting from the first word.
• Query is evaluated for each item in the list. If query succeeds, item is processed, if query fails, item is ignored.
• Query is evaluated using a stack of boolean values. Initially stack contains infinite amount of 'true' values. At the end of evaluation, if stack contains at least one 'false' value, query fails.
• Query words operate according to the following rules:

?name	pushes 'true' if item has value of property name, 'false' if it does not.
?-name	pushes 'true' if item does not have value of property name, 'false' otherwise.
?name=x ?=name=x	pushes 'true' if property name has value equal to x, 'false' otherwise.
?<name=x	pushes 'true' if property name has value less than x, 'false' otherwise.
?>name=x	pushes 'true' if property name has value greater than x, 'false' otherwise.
?#operations	applies operations to the values in the stack. operation string is evaluated left to right. sequence of decimal digits followed by any other character or end of word is interpreted as a stack index. top value has index 0. index that is followed by a character pushes copy of value at that index. index that is followed by the end of word replaces all values with the value at that index. ! character replaces top value with the opposite. & pops two values and pushes result of logical 'and' operation. | pops two values and pushes result of logical 'or' operation. . after an index does nothing. . after another character pushes copy of top value.

Examples:

• Get all ethernet and VLAN interfaces:

/interface/print
?type=ether
?type=vlan
?#|

• Get all routes that have non-empty comment:

/ip/route/print
?>comment=

OID

print command can return OID values for properties that are available in SNMP. This feature appeared in 3.23 version.

In console, OID values can be seen by running 'print oid' command. In API, these properties have name that ends with ".oid", and can be retrieved by adding their name to the value of '.proplist'. An example:

Template:Apic

Template:Apic

Template:Apic

Template:Apis

Template:Apis

Template:Apis

Template:Apis

Template:Apis

Template:Apis

Template:Apis

Template:Apis

Command examples

/system/package/getall

Template:Bapi Template:Apic Template:Apic Template:Apis Template:Apis Template:Apis Template:Apis Template:Apis Template:Apis Template:Apis Template:Apis Template:Apis Template:Apis Template:Apis Template:Apis Template:Apis Template:Apis Template:Apis Template:Apis |- | ... more !re sentences ... |- Template:Apis Template:Apis Template:Apis Template:Apis Template:Apis Template:Apis Template:Apis Template:Apis Template:Apis Template:Apis Template:Eapi

/user/active/listen

Template:Bapi Template:Apic Template:Apic Template:Apis Template:Apis Template:Apis Template:Apis Template:Apis Template:Apis Template:Apis Template:Apis Template:Apis Template:Apis Template:Apis Template:Apis |- | ... more !re sentences ... |- Template:Eapi

Example client

• this is simple API client in Python2
• example for Python3
• usage: api.py ip-address username password
• after that type words from keyboard, terminating them with newline
• Since empty word terminates sentence, you should press enter twice after last word before sentence will be sent to router.

#!/usr/bin/python

import sys, posix, time, md5, binascii, socket, select

class ApiRos:
    "Routeros api"
    def __init__(self, sk):
        self.sk = sk
        self.currenttag = 0
        
    def login(self, username, pwd):
        for repl, attrs in self.talk(["/login"]):
            chal = binascii.unhexlify(attrs['=ret'])
        md = md5.new()
        md.update('\x00')
        md.update(pwd)
        md.update(chal)
        self.talk(["/login", "=name=" + username,
                   "=response=00" + binascii.hexlify(md.digest())])

    def talk(self, words):
        if self.writeSentence(words) == 0: return
        r = []
        while 1:
            i = self.readSentence();
            if len(i) == 0: continue
            reply = i[0]
            attrs = {}
            for w in i[1:]:
                j = w.find('=', 1)
                if (j == -1):
                    attrs[w] = ''
                else:
                    attrs[w[:j]] = w[j+1:]
            r.append((reply, attrs))
            if reply == '!done': return r

    def writeSentence(self, words):
        ret = 0
        for w in words:
            self.writeWord(w)
            ret += 1
        self.writeWord('')
        return ret

    def readSentence(self):
        r = []
        while 1:
            w = self.readWord()
            if w == '': return r
            r.append(w)
            
    def writeWord(self, w):
        print "<<< " + w
        self.writeLen(len(w))
        self.writeStr(w)

    def readWord(self):
        ret = self.readStr(self.readLen())
        print ">>> " + ret
        return ret

    def writeLen(self, l):
        if l < 0x80:
            self.writeStr(chr(l))
        elif l < 0x4000:
            l |= 0x8000
            self.writeStr(chr((l >> 8) & 0xFF))
            self.writeStr(chr(l & 0xFF))
        elif l < 0x200000:
            l |= 0xC00000
            self.writeStr(chr((l >> 16) & 0xFF))
            self.writeStr(chr((l >> 8) & 0xFF))
            self.writeStr(chr(l & 0xFF))
        elif l < 0x10000000:        
            l |= 0xE0000000         
            self.writeStr(chr((l >> 24) & 0xFF))
            self.writeStr(chr((l >> 16) & 0xFF))
            self.writeStr(chr((l >> 8) & 0xFF))
            self.writeStr(chr(l & 0xFF))
        else:                       
            self.writeStr(chr(0xF0))
            self.writeStr(chr((l >> 24) & 0xFF))
            self.writeStr(chr((l >> 16) & 0xFF))
            self.writeStr(chr((l >> 8) & 0xFF))
            self.writeStr(chr(l & 0xFF))

    def readLen(self):              
        c = ord(self.readStr(1))    
        if (c & 0x80) == 0x00:      
            pass                    
        elif (c & 0xC0) == 0x80:    
            c &= ~0xC0              
            c <<= 8                 
            c += ord(self.readStr(1))    
        elif (c & 0xE0) == 0xC0:    
            c &= ~0xE0              
            c <<= 8                 
            c += ord(self.readStr(1))    
            c <<= 8                 
            c += ord(self.readStr(1))    
        elif (c & 0xF0) == 0xE0:    
            c &= ~0xF0              
            c <<= 8                 
            c += ord(self.readStr(1))    
            c <<= 8                 
            c += ord(self.readStr(1))    
            c <<= 8                 
            c += ord(self.readStr(1))    
        elif (c & 0xF8) == 0xF0:    
            c = ord(self.readStr(1))     
            c <<= 8                 
            c += ord(self.readStr(1))    
            c <<= 8                 
            c += ord(self.readStr(1))    
            c <<= 8                 
            c += ord(self.readStr(1))    
        return c                    

    def writeStr(self, str):        
        n = 0;                      
        while n < len(str):         
            r = self.sk.send(str[n:])
            if r == 0: raise RuntimeError, "connection closed by remote end"
            n += r                  

    def readStr(self, length):      
        ret = ''                    
        while len(ret) < length:    
            s = self.sk.recv(length - len(ret))
            if s == '': raise RuntimeError, "connection closed by remote end"
            ret += s
        return ret

def main():
    s = socket.socket(socket.AF_INET, socket.SOCK_STREAM)
    s.connect((sys.argv[1], 8728))  
    apiros = ApiRos(s);             
    apiros.login(sys.argv[2], sys.argv[3]);

    inputsentence = []

    while 1:
        r = select.select([s, sys.stdin], [], [], None)
        if s in r[0]:
            # something to read in socket, read sentence
            x = apiros.readSentence()

        if sys.stdin in r[0]:
            # read line from input and strip off newline
            l = sys.stdin.readline()
            l = l[:-1]

            # if empty line, send sentence and start with new
            # otherwise append to input sentence
            if l == '':
                apiros.writeSentence(inputsentence)
                inputsentence = []
            else:
                inputsentence.append(l)

if __name__ == '__main__':
    main()

Example run:

debian@localhost:~/api-test$ ./api.py 10.0.0.1 admin ''
<<< /login
<<< 
>>> !done
>>> =ret=93b438ec9b80057c06dd9fe67d56aa9a
>>> 
<<< /login
<<< =name=admin
<<< =response=00e134102a9d330dd7b1849fedfea3cb57
<<< 
>>> !done
>>> 
/user/getall

<<< /user/getall
<<< 
>>> !re
>>> =.id=*1
>>> =disabled=no
>>> =name=admin
>>> =group=full
>>> =address=0.0.0.0/0
>>> =netmask=0.0.0.0
>>> 
>>> !done
>>> 

See also

• API command notes

API examples in the Wiki

• in PHP
• in Delphi #1
• in Delphi #2

• in C
• API in C++
• in C#

• in Flash Actionscript 3
• in Ruby on rails
• in VB .NET
• in java
• in NodeJS
• Python3
• in C using winsock

API examples on the MikroTik Forum

• in Perl by Hugh
• in Delphi by Rodolfo
• in Delphi #2 by Chupaka
• in NodeJS by Trakkasure
• in VB by lucho512
• on PHP for sparks framework by vthinkteam

API exmaples elsewhere

• in .NET (C#) high-level api solution by danikf
• C++ libraries
• in PHP by boen_robot