docs-v2/content/influxdb/cloud-serverless/api-compatibility/v2/_index.md

title	list_title	description	weight	menu	influxdb/cloud-serverless/tags	aliases
Use the InfluxDB v2 API with InfluxDB Cloud Serverless	InfluxDB v2 API compatibility	Use the InfluxDB v2 API for new write workloads and existing v2 write workloads. InfluxDB Cloud Serverless is compatible with the InfluxDB v2 API `/api/v2/write` endpoint and existing InfluxDB 2.x tools and code.	1	influxdb_cloud_serverless parent name API compatibility v2 API	write line protocol	/influxdb/cloud-serverless/primers/api/v2/

{{% cloud-name %}} 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 {{% cloud-name %}}.

InfluxDB v2 API endpoints won't work for managing resources or querying data in {{% cloud-name %}}. To query data, use the Flight+gRPC protocol or the InfluxDB v1 /query HTTP API endpoint and associated tools.

• Authenticate API requests
  • Authenticate with a token
    • Syntax
    • Examples
• Responses
  • Error examples
• Write data
  • /api/v2/write parameters
    • Timestamp precision
  • Tools for writing to the v2 API
    • Telegraf
    • Interactive clients
    • Client libraries
• Query data
  • Tools to execute queries
  • /api/v2/query not supported

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.

Syntax

Authorization: Token API_TOKEN

Examples

Use Token to authenticate a write request:

{{% code-placeholders "BUCKET_NAME|API_TOKEN" %}}

# Use the Token authentication scheme with /api/v2/write
curl --post "https://cloud2.influxdata.com/api/v2/write?bucket=BUCKET_NAME&precision=s" \
  --header "Authorization: Token API_TOKEN" \
  --data-binary 'home,room=kitchen temp=72 1463683075'

{{% /code-placeholders %}}

Replace the following:

• {{% code-placeholder-key %}}BUCKET_NAME{{% /code-placeholder-key %}}: your InfluxDB Cloud Serverless bucket
• {{% code-placeholder-key %}}API_TOKEN{{% /code-placeholder-key %}}: an API token with sufficient permissions to the database

Responses

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 {{% cloud-name %}} 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-endpoint endpoint="https://cloud2.influxdata.com/api/v2/write" method="post"%}}

• /api/v2/write parameters
• Tools for writing to the v2 API

/api/v2/write parameters

For {{% cloud-name %}} v2 API /api/v2/write requests, set parameters as listed in the following table:

Parameter	Allowed in	Ignored	Value
org	Query string	Ignored	Non-zero-length string (ignored, but can't be empty)
orgID	Query string	Ignored	N/A
bucket {{% req " *" %}}	Query string	Honored	Database name
precision	Query string	Honored	Timestamp precision
Accept	Header	Honored	User-defined
Authorization {{% req " *" %}}	Header	Honored	Token API_TOKEN
Content-Encoding	Header	Honored	gzip (compressed data) or identity (uncompressed)
Content-Length	Header	Honored	User-defined
Content-Type	Header	Ignored	N/A (only supports line protocol)
Zap-Trace-Span	Header	Ignored

{{% caption %}}{{% req " *" %}} = {{% req "Required" %}}{{% /caption %}}

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 {{% cloud-name %}} /api/v2/write endpoint:

• Telegraf
• Interactive clients
• Client libraries

Telegraf

See how to configure Telegraf to write to {{% cloud-name %}}.

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.
• InfluxDB v1 API /query request that contains an InfluxQL query.

{{% note %}}

Tools to execute queries

{{% cloud-name %}} supports many different tools for querying data, including:

• influx3 data CLI
• InfluxDB v3 client libraries
• Flight clients
• Superset
• Grafana
• InfluxQL with InfluxDB v1 HTTP API
• [Chronograf](/{{< latest "Chronograf" >}}/)

{{% /note %}}

/api/v2/query not supported

The /api/v2/query API endpoint and associated tooling aren't supported in {{% cloud-name %}}.