API Endpoints & Ports

This is archived documentation for InfluxData product versions that are no longer maintained. For newer documentation, see the latest InfluxData documentation.


All current API Endpoints are listed below.


The ping endpoint accepts both GET and HEAD HTTP requests. The response body is empty. The version of the InfluxDB server you issued the request to can be extracted through the X-Influxdb-Version field of the header. For example this is the response from a server running 0.12.0 of InfluxDB:

$ curl -sl -I localhost:8086/ping

HTTP/1.1 204 No Content
Request-Id: 7d641f0b-e23b-11e5-8005-000000000000
X-Influxdb-Version: 0.12.0
Date: Fri, 04 Mar 2016 19:01:23 GMT


For more information on the /query endpoint see the Querying Data section of our docs.


For more information on the /write endpoint see the Writing Data section of our docs.



By default the InfluxDB HTTP API listens on port 8086. The /ping, /write, and /query endpoints are all part of the HTTP API.

Admin interface port

The admin interface for InfluxDB runs on port 8083 and exposes web UI for the server.

Secondary Ports

InfluxDB also supports communication through UDP, Graphite, Collectd, and OpenTSDB.

Default ports:

  • Graphite: 2003
  • OpenTSDB: 4242

No default ports are assigned for UDP and Collectd.