Use the InfluxDB v2 API with InfluxDB Cloud Dedicated
Use the InfluxDB v2 API /api/v2/write
endpoint for new write workloads and existing v2 write workloads that you bring to InfluxDB Cloud Dedicated.
Learn how to authenticate requests, adjust request parameters for existing v2 workloads, and find compatible tools for writing and querying data stored in an InfluxDB Cloud Dedicated database.
For help finding the best workflow for your situation, contact Support.
Authenticate API requests
InfluxDB API endpoints require each request to be authenticated with a database token.
Authenticate with a token
Use the Authorization: Bearer
scheme or the Authorization: Token
scheme to
pass a database token
that has the necessary permissions for the operation.
Bearer
and Token
are equivalent in InfluxDB Cloud Dedicated.
The Token
scheme is used in the InfluxDB 2.x API.
Bearer
is defined by the OAuth 2.0 Framework.
Support for one or the other may vary across InfluxDB API clients.
Syntax
Authorization: Bearer DATABASE_TOKEN
Authorization: Token DATABASE_TOKEN
Examples
Use Bearer
to authenticate a write request:
########################################################
# Use the Bearer authorization scheme with /api/v2/write
# to write data.
########################################################
curl --request post 'https://cluster-id.a.influxdb.io/api/v2/write?bucket=DATABASE_NAME&precision=s' \
--header 'Authorization: Bearer DATABASE_TOKEN' \
--data-binary 'home,room=kitchen temp=72 1463683075'
Use Token
to authenticate a write request:
########################################################
# Use the Token authentication scheme with /api/v2/write
# to write data.
########################################################
curl --request post "https://cluster-id.a.influxdb.io/api/v2/write?bucket=DATABASE_NAME&precision=s" \
--header "Authorization: Token DATABASE_TOKEN" \
--data-binary 'home,room=kitchen temp=72 1463683075'
Replace the following:
DATABASE_NAME
: your InfluxDB Cloud Dedicated databaseDATABASE_TOKEN
: a database token with sufficient permissions to the specified database
Responses
InfluxDB HTTP API responses use standard HTTP status codes.
The response body for partial writes and errors contains a JSON object with code
and message
properties that describe the error.
Response body messages may differ across InfluxDB Cloud Dedicated 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 database 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
Use the InfluxDB v2 API /api/v2/write
endpoint for new write workloads and existing v2 workloads.
POST https://cluster-id.a.influxdb.io/api/v2/write
/api/v2/write parameters
For InfluxDB Cloud Dedicated 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 * | Query string | Honored | Database name |
precision | Query string | Honored | Timestamp precision |
Accept | Header | Honored | User-defined |
Authorization * |
Header | Honored | Bearer DATABASE_TOKEN or Token DATABASE_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 |
Timestamp precision
Use one of the following precision
values in v2 API /api/v2/write
requests:
ns
: nanosecondsus
: microsecondsms
: millisecondss
: secondsm
: minutesh
: hours
Tools for writing to the v2 API
The following tools work with the InfluxDB Cloud Dedicated /api/v2/write
endpoint:
Telegraf
See how to configure Telegraf to write to InfluxDB Cloud Dedicated.
Interactive clients
To test InfluxDB v2 API writes interactively, 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.
influx CLI not supported
Don’t use the influx
CLI with InfluxDB Cloud Dedicated.
While it may coincidentally work, it isn’t officially supported.
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 Cloud Dedicated 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 Dedicated 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 Dedicated supports many different tools for querying data, including:
/api/v2/query not supported
The /api/v2/query
API endpoint and associated tooling, such as the influx
CLI and InfluxDB v2 client libraries, aren’t supported in InfluxDB Cloud Dedicated.
Was this page helpful?
Thank you for your feedback!
Support and feedback
Thank you for being part of our community! We welcome and encourage your feedback and bug reports for InfluxDB and this documentation. To find support, use the following resources:
Customers with an annual or support contract can contact InfluxData Support.