Skip to content

Using the API


Versioning an API is a minefield which saw us looking at numerous options on how to do this.

We have currently settled on using versioning within the API end point itself /api/v0. As the API itself is new and still in active development we also decided that v0 would be the best starting point to indicate it's in development.


To access any of the token end points you will be required to authenticate using a token. Tokens can be created directly from within the LibreNMS web interface by going to /api-access/.

  • Click on 'Create API access token'.
  • Select the user you would like to generate the token for.
  • Enter an optional description.
  • Click Create API Token.


Whilst this documentation will describe and show examples of the end points, we've designed the API so you should be able to traverse through it without knowing any of the available API routes.

You can do this by first calling /api/v0:

curl -H 'X-Auth-Token: YOURAPITOKENHERE'


 "list_bgp": "",
 "edit_rule": ""


Input to the API is done in three different ways, sometimes a combination of two or three of these.

  • Passing parameters via the api route. For example when obtaining a devices details you will pass the hostname of the device in the route: /api/v0/devices/:hostname.
  • Passing parameters via the query string. For example you can list all devices on your install but limit the output to devices that are currently down: /api/v0/devices?type=down
  • Passing data in via JSON, this will mainly be used when adding or updating information via the API, for instance adding a new device:
curl -X POST -d '{"hostname":"localhost.localdomain","version":"v1","community":"public"}' -H 'X-Auth-Token: YOURAPITOKENHERE'


Output from the API currently is via two output types:

  • JSON: Most API responses will output json. As shown in the example for calling the API endpoint.
  • PNG: This is for when the request is for an image such as a graph for a switch port.

Endpoint Categories