Documentation

/query 1.x compatibility API

This page documents an earlier version of InfluxDB OSS. InfluxDB 3 Core is the latest stable version.

The /query 1.x compatibility endpoint queries InfluxDB 2.7 using InfluxQL. Send an InfluxQL query in an HTTP GET or POST request to query data from the /query endpoint.

The /query compatibility endpoint uses the database and retention policy specified in the query request to map the request to an InfluxDB bucket. For more information, see Database and retention policy mapping.

Authentication

Use one of the following authentication methods:

  • the 2.x Authorization: Token scheme in the header
  • the v1-compatible u and p query string parameters
  • the v1-compatible Basic authentication scheme in the header

For more information, see Authentication for the 1.x compatibility API.

Query string parameters

u

(Optional) The 1.x username to authenticate the request. If you provide an API token as the password, u is required, but can be any value. See query string authentication.

p

(Optional) The 1.x password or the 2.x API token to authenticate the request. See query string authentication.

db

(Required) The database to query data from. This is mapped to an InfluxDB bucket. See Database and retention policy mapping.

rp

The retention policy to query data from. This is mapped to an InfluxDB bucket. See Database and retention policy mapping.

q

(Required) The InfluxQL query to execute. To execute multiple queries, delimit queries with a semicolon (;).

epoch

Return results with Unix timestamps (also known as epoch timestamps) in the specified precision instead of RFC3339 timestamps with nanosecond precision. The following precisions are available:

  • ns - nanoseconds
  • u or µ - microseconds
  • ms - milliseconds
  • s - seconds
  • m - minutes
  • h - hours

Query examples

Query using basic authentication

The following example:

  • sends a GET request to the /query endpoint
  • uses the Authorization header with the Basic scheme (compatible with InfluxDB 1.x) to provide username and password credentials
  • uses the default retention policy for the database
##############################################################################
# Use Basic authentication with an
# InfluxDB v1-compatible username and password
# to query the InfluxDB 1.x compatibility API.
#
# 
INFLUX_USERNAME
: your v1-compatible username.
#
INFLUX_PASSWORD_OR_TOKEN
: your API token or v1-compatible password.
############################################################################## curl --get "http://localhost:8086/query" \ --user "
INFLUX_USERNAME
:
INFLUX_PASSWORD_OR_TOKEN
"
\
--data-urlencode "db=BUCKET_NAME" \ --data-urlencode "q=SELECT * FROM cpu_usage"
Query using an HTTP POST request
curl \
  --request POST \
  "http://localhost:8086/query?db=DATABASE_NAME&rp=RETENTION_POLICY" \
  --user "
INFLUX_USERNAME
:
INFLUX_PASSWORD_OR_TOKEN
"
\
--header "Content-type: application/vnd.influxql" \ --data "SELECT * FROM cpu_usage WHERE time > now() - 1h"
Query a non-default retention policy

The following example:

  • sends a GET request to the /query endpoint
  • uses the Authorization header with the Token scheme (compatible with InfluxDB 2.x) to provide the API token
  • queries a custom retention policy mapped for the database
curl --get http://localhost:8086/query \
  --header "Authorization: Token 
API_TOKEN
"
\
--data-urlencode "db=DATABASE_NAME" \ --data-urlencode "rp=RETENTION_POLICY_NAME" \ --data-urlencode "q=SELECT used_percent FROM mem WHERE host=host1"
Execute multiple queries
curl --get http://localhost:8086/query \
  --header "Authorization: Token 
API_TOKEN
"
\
--data-urlencode "db=DATABASE_NAME" \ --data-urlencode "q=SELECT * FROM mem WHERE host=host1;SELECT mean(used_percent) FROM mem WHERE host=host1 GROUP BY time(10m)"
Return query results with millisecond Unix timestamps
curl --get http://localhost:8086/query \
  --header "Authorization: Token 
API_TOKEN
"
\
--data-urlencode "db=DATABASE_NAME" \ --data-urlencode "rp=RETENTION_POLICY_NAME" \ --data-urlencode "q=SELECT used_percent FROM mem WHERE host=host1" \ --data-urlencode "epoch=ms"
Execute InfluxQL queries from a file
curl --get http://localhost:8086/query \
  --header "Authorization: Token 
API_TOKEN
"
\
--data-urlencode "db=DATABASE_NAME" \ --data-urlencode "q@path/to/influxql.txt"
Return a gzip-compressed response
curl --get http://localhost:8086/query \
  --header 'Accept-Encoding: gzip' \
  --header "Authorization: Token 
API_TOKEN
"
\
--data-urlencode "db=DATABASE_NAME" \ --data-urlencode "q=SELECT used_percent FROM mem WHERE host=host1"

Replace the following:

  • API_TOKEN: your InfluxDB API token
  • DATABASE_NAME: the name of the database to query. In InfluxDB 2.x, databases and retention policies map to buckets.
  • RETENTION_POLICY_NAME: the name of the retention policy to query. In InfluxDB 2.x, databases and retention policies map to buckets.

For more information about the database and retention policy mapping, see Database and retention policy mapping.


Was this page helpful?

Thank you for your feedback!


New in InfluxDB 3.5

Key enhancements in InfluxDB 3.5 and the InfluxDB 3 Explorer 1.3.

See the Blog Post

InfluxDB 3.5 is now available for both Core and Enterprise, introducing custom plugin repository support, enhanced operational visibility with queryable CLI parameters and manual node management, stronger security controls, and general performance improvements.

InfluxDB 3 Explorer 1.3 brings powerful new capabilities including Dashboards (beta) for saving and organizing your favorite queries, and cache querying for instant access to Last Value and Distinct Value caches—making Explorer a more comprehensive workspace for time series monitoring and analysis.

For more information, check out:

InfluxDB Docker latest tag changing to InfluxDB 3 Core

On November 3, 2025, the latest tag for InfluxDB Docker images will point to InfluxDB 3 Core. To avoid unexpected upgrades, use specific version tags in your Docker deployments.

If using Docker to install and run InfluxDB, the latest tag will point to InfluxDB 3 Core. To avoid unexpected upgrades, use specific version tags in your Docker deployments. For example, if using Docker to run InfluxDB v2, replace the latest version tag with a specific version tag in your Docker pull command–for example:

docker pull influxdb:2