Use the InfluxDB v2 API with InfluxDB Cloud Serverless

InfluxDB Cloud Serverless is compatible with the InfluxDB v2 API /api/v2/write endpoint and existing InfluxDB 2.x tools and code. Use the InfluxDB v2 API for new write workloads and existing v2 write workloads that you bring to InfluxDB Cloud Serverless.

InfluxDB v2 API endpoints won’t work for managing resources or querying data in InfluxDB Cloud Serverless. To query data, use the Flight+gRPC protocol or the InfluxDB v1 /query HTTP API endpoint and associated tools.

Authenticate API requests

InfluxDB API endpoints require each request to be authenticated with an API token.

Authenticate with a token

Use the Authorization: Token scheme to pass an API token that has the necessary permissions for the operation.

The Token scheme is used in the InfluxDB 2.x API.


Authorization: Token API_TOKEN


Use Token to authenticate a write request:

# Use the Token authentication scheme with /api/v2/write
curl --post "
--header "Authorization: Token
--data-binary 'home,room=kitchen temp=72 1463683075'

Replace the following:

  • BUCKET_NAME: your InfluxDB Cloud Serverless bucket
  • API_TOKEN: an API token with sufficient permissions to the database


InfluxDB API responses use standard HTTP status codes. For successful writes, InfluxDB responds with a 204 No Content status code. Error responses contain a JSON object with code and message properties that describe the error. Response body messages may differ across InfluxDB Cloud Serverless v1 API, v2 API, InfluxDB Cloud, and InfluxDB OSS.

Error examples

  • Missing bucket value

    400 Bad Request
    { "code": "invalid",
      "message":"missing bucket value"

    The ?bucket= parameter value is missing in the request. Provide the bucket name.

  • Failed to deserialize org/bucket/precision

    400 Bad Request
    { "code": "invalid",
      "message":"failed to deserialize org/bucket/precision in request: unknown variant `u`, expected one of `s`, `ms`, `us`, `ns`"

    The ?precision= parameter contains an unknown value. Provide a timestamp precision.

Write data

We recommend using the InfluxDB v2 API /api/v2/write endpoint for new write workloads and existing v2 workloads.


/api/v2/write parameters

For InfluxDB Cloud Serverless v2 API /api/v2/write requests, set parameters as listed in the following table:

ParameterAllowed inIgnoredValue
orgQuery stringIgnoredNon-zero-length string (ignored, but can’t be empty)
orgIDQuery stringIgnoredN/A
bucket *Query stringHonoredDatabase name
precisionQuery stringHonoredTimestamp precision
Authorization *HeaderHonoredToken API_TOKEN
Content-EncodingHeaderHonoredgzip (compressed data) or identity (uncompressed)
Content-TypeHeaderIgnoredN/A (only supports line protocol)
* = Required

Timestamp precision

Use one of the following precision values in v2 API /api/v2/write requests:

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

Tools for writing to the v2 API

The following tools work with the InfluxDB Cloud Serverless /api/v2/write endpoint:


See how to configure Telegraf to write to InfluxDB Cloud Serverless.

Interactive clients

To test InfluxDB v2 API writes interactively from the command line, use the influx3 data CLI or common HTTP clients such as cURL and Postman.

To setup and start using interactive clients, see the Get started tutorial.

Client libraries

InfluxDB v3 client libraries and v2 client libraries can write data to the InfluxDB v2 API /api/v2/write endpoint. Client libraries are language-specific packages that integrate InfluxDB APIs with your application.

To setup and start using client libraries, see the Get started tutorial.

Query data

InfluxDB v3 provides the following protocols for executing a query:

  • Flight+gRPC request that contains an SQL or InfluxQL query. To learn how to query InfluxDB Cloud Serverless using Flight and SQL, see the Get started tutorial.
  • InfluxDB v1 API /query request that contains an InfluxQL query.

Tools to execute queries

InfluxDB Cloud Serverless supports many different tools for querying data, including:

/api/v2/query not supported

The /api/v2/query API endpoint and associated tooling aren’t supported in InfluxDB Cloud Serverless.

Was this page helpful?

Thank you for your feedback!

Introducing InfluxDB Clustered

A highly available InfluxDB 3.0 cluster on your own infrastructure.

InfluxDB Clustered is a highly available InfluxDB 3.0 cluster built for high write and query workloads on your own infrastructure.

InfluxDB Clustered is currently in limited availability and is only available to a limited group of InfluxData customers. If interested in being part of the limited access group, please contact the InfluxData Sales team.

Learn more
Contact InfluxData Sales

The future of Flux

Flux is going into maintenance mode. You can continue using it as you currently are without any changes to your code.

Flux is going into maintenance mode and will not be supported in InfluxDB 3.0. This was a decision based on the broad demand for SQL and the continued growth and adoption of InfluxQL. We are continuing to support Flux for users in 1.x and 2.x so you can continue using it with no changes to your code. If you are interested in transitioning to InfluxDB 3.0 and want to future-proof your code, we suggest using InfluxQL.

For information about the future of Flux, see the following:

State of the InfluxDB Cloud Serverless documentation

InfluxDB Cloud Serverless documentation is a work in progress.

The new documentation for InfluxDB Cloud Serverless is a work in progress. We are adding new information and content almost daily. Thank you for your patience!

If there is specific information you’re looking for, please submit a documentation issue.

InfluxDB Cloud Serverless