Documentation

InfluxDB Cloud Serverless

Use the InfluxDB v1 HTTP query API and InfluxQL

  • InfluxQL

Use the InfluxDB v1 HTTP API /query endpoint and InfluxQL to query data stored in InfluxDB Cloud Serverless and return results in JSON or CSV format. The /query endpoint provides compatibility for InfluxDB 1.x workloads that you bring to InfluxDB 3.

Before you can use the v1 query API, databases and retention policies must be mapped to buckets.

Flight queries don’t use DBRP mappings

When using Flight RPC or Flight SQL to query InfluxDB, specify the bucket name. Flight queries don’t use DBRP mappings. See how to get started querying with Flight and SQL or InfluxQL.

Query the v1 /query endpoint

To query using HTTP and InfluxQL, send a GET or POST request to the v1 /query endpoint.

GET https://cloud2.influxdata.com/query

Parameters

For InfluxDB Cloud Serverless v1 API /query requests, set parameters as listed in the following table:

ParameterAllowed inIgnoredValue
chunkedQuery stringHonoredReturns points in streamed batches instead of in a single response. If set to true, InfluxDB chunks responses by series or by every 10,000 points, whichever occurs first.
chunked_sizeQuery stringHonoredRequires chunked to be set to true. If set to a specific value, InfluxDB chunks responses by series or by this number of points.
dbQuery stringHonoredDatabase name mapped to a bucket
epochQuery stringHonoredTimestamp precision
prettyQuery stringIgnoredN/A
rpQuery stringHonoredRetention policy mapped to a bucket
qQuery stringHonoredInfluxQL
Authorization header or u and pToken

When bringing v1 API workloads to InfluxDB Cloud Serverless, you’ll need to adjust request parameters in your client configuration or code.

Timestamp precision

Use one of the following values for timestamp precision (epoch):

  • ns: nanoseconds
  • us: microseconds
  • ms: milliseconds
  • s: seconds
  • m: minutes
  • h: hours

Authorization

To authorize a query request, include a token that has read permission for the bucket. Use Token authentication or v1-compatible username and password authentication to include a token in the request.

Return results as JSON or CSV

By default, the /query endpoint returns results in JSON format.

To return results in CSV format, include the Accept header with the application/csv or text/csv MIME type–for example:

curl --get https://cloud2.influxdata.com/query \
  --header "Authorization: Token 
DATABASE_TOKEN
" \
  --header "Accept: application/csv" \
  --data-urlencode "db=
DATABASE_NAME
" \
  --data-urlencode "q=SELECT * FROM home"

Tools for querying the v1 API

Interactive clients

To test InfluxDB v1 API queries interactively from the command line, use common HTTP clients such as cURL and Postman.

Token Auth Basic Auth Query String Auth

curl https://cloud2.influxdata.com/query \
  --header "Authorization: Token 
API_TOKEN
" \
  --data-urlencode "db=
DATABASE_NAME
" \
  --data-urlencode "q=SELECT * FROM home"

Replace the following:

curl --get https://cloud2.influxdata.com/query \
  -user "":"API_TOKEN" \
  --data-urlencode "db=
DATABASE_NAME
" \
  --data-urlencode "q=SELECT * FROM home"
curl --get https://cloud2.influxdata.com/query \
  --data-urlencode "u=ignored" \
  --data-urlencode "p=
DATABASE_TOKEN
" \
  --data-urlencode "db=
DATABASE_NAME
" \
  --data-urlencode "q=SELECT * FROM home"

Troubleshoot failures

Troubleshoot problems and errors encountered when using the HTTP API to query InfluxDB Cloud Serverless.

Database not found

If a DBRP doesn’t exist for the db=DATABASE_NAME and rp=RETENTION_POLICY_NAME combination in the query request, the response body contains an error message, for example "database not found:...".

Quota and limit errors

HTTP API /query requests are subject to usage quotas and limits.

Was this page helpful?

Thank you for your feedback!

© 2026 InfluxData, Inc.

Select your InfluxDB Cloud Serverless region

Select your InfluxDB Cloud Serverless region and we’ll customize code examples for you.

AWS

For more information, see InfluxDB Cloud Serverless regions.

Thank you for your feedback!

Let us know what we can do better:

Thank you!

No thanks

InfluxDB OSS 2.9.0: API tokens are hashed by default

Stronger token security in InfluxDB OSS 2.9.0 — tokens are hashed on disk by default. Existing tokens are hashed on first startup and can’t be recovered afterward. Capture any plaintext tokens you still need before you upgrade.

View InfluxDB OSS 2.9.0 release notes

Hashed tokens authenticate exactly like unhashed tokens — clients and integrations keep working.

Also new in 2.9.0:

  • Configurable backup compression
  • Restore support for backups containing hashed tokens
  • Tighter Edge Data Replication queue validation
  • Flux upgrade
  • Compaction reliability improvements

Key enhancements in Explorer 1.9

Explorer 1.9 is now available with InfluxQL support, an AI-assisted Flux to SQL converter (beta), and new live sample data simulators.

View Explorer 1.9 release notes

Explorer 1.9 includes new features and improvements that make it easier to query, visualize, and manage data.

Highlights:

  • Flux to SQL converter (beta): Convert Flux queries to SQL with an AI-assisted converter.
  • InfluxQL support: Query data with InfluxQL in the Data Explorer and dashboards, and save and load InfluxQL queries.
  • InfluxQL visualizations: Render line and bar charts from InfluxQL results with per-tag series grouping.
  • Query error history: Review a history of query errors in the query tool.
  • Live sample data simulators: Generate continuous live sample data with new bird data and signal generator simulators.

For more details, see Explorer 1.9 release notes

InfluxDB 3.10 is now available

InfluxDB 3 Core 3.10 adds an automatic catalog format upgrade, a configurable query-concurrency limit, and processing engine improvements.

Key updates in InfluxDB 3 Core 3.10:

  • Catalog format upgrade: the on-disk catalog automatically upgrades from format v2 to v3 on first 3.10 startup. Migration is one-way—back up your catalog before upgrading.
  • --max-concurrent-queries: limit concurrent queries (adjustable at runtime).
  • GET /ready endpoint for readiness probes.
  • Processing engine: cross-database queries and trigger lockdown flags.

For more information, see the InfluxDB 3 Core release notes.

InfluxDB 3.10 is now available

InfluxDB 3 Enterprise 3.10 adds automated backup and restore, row-level deletions, and user management, with an automatic catalog format upgrade and performance preview improvements.

Key updates in InfluxDB 3 Enterprise 3.10:

  • Catalog format upgrade: the on-disk catalog automatically upgrades from format v2 to v3 on first 3.10 startup. Migration is one-way—back up your catalog before upgrading.
  • Automated backup and restore (beta)
  • Row-level deletions
  • User management (authentication and RBAC) — preview
  • Performance preview improvements

Backup and restore, row-level deletions, and the performance preview require the Enterprise storage engine upgrade (opt-in beta). Beta and preview features are subject to breaking changes and aren’t recommended for production use.

For more information, see the InfluxDB 3 Enterprise release notes

Telegraf Enterprise is now generally available

Telegraf Enterprise is now generally available, along with Telegraf Controller v1.0.

Telegraf Enterprise combines Telegraf Controller, a centralized management console for Telegraf, with official support from InfluxData. Manage configurations, monitor fleet health, and operate tens of thousands of Telegraf agents from a single system.

InfluxDB Docker latest tag changing to InfluxDB 3 Core

On September 15, 2026, 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

InfluxDB Cloud Serverless

You are currently viewing documentation specific to InfluxDB Cloud Serverless powered by the v3 storage engine, which offers different functionality than InfluxDB Cloud powered by the TSM storage engine.

Are you using InfluxDB Cloud Serverless? How to find out?

Visit your organization's homepage and find the following at the bottom of the right column:

InfluxDB Cloud Serverless Storage Engine Version 3
Yes – I'm using InfluxDB Cloud Serverless No – I'm using InfluxDB Cloud (TSM)