Documentation

influxdb3 write

The influxdb3 write command writes data to your InfluxDB 3 Enterprise server.

Usage

influxdb3 write [OPTIONS] --database <DATABASE_NAME> [LINE_PROTOCOL]...
Aliases

write, w

Arguments

  • LINE_PROTOCOL: The line protocol to write to InfluxDB 3 Enterprise. Provide the line protocol in one of the following ways:

    • a string
    • a path to a file that contains the line protocol using the --file option
    • from stdin

Options

OptionDescription
-H--hostHost URL of the running InfluxDB 3 Enterprise server (default is http://127.0.0.1:8181)
-d--database(Required) Name of the database to operate on
--token(Required) Authentication token
-f--fileA file that contains line protocol to write
--accept-partialAccept partial writes
--no-syncDo not wait for WAL sync before acknowledging the write request
--precisionPrecision of data timestamps (ns, us, ms, or s)
--tls-caPath to a custom TLS certificate authority (for testing or self-signed certificates)
--tls-no-verifyDisable TLS certificate verification (Not recommended in production, useful for self-signed certificates)
-h--helpPrint help information
--help-allPrint detailed help information

Option environment variables

You can use the following environment variables to set command options:

Environment VariableOption
INFLUXDB3_HOST_URL--host
INFLUXDB3_DATABASE_NAME--database
INFLUXDB3_AUTH_TOKEN--token
INFLUXDB3_TLS_NO_VERIFY--tls-no-verify

Examples

In the examples below, replace the following:

  • DATABASE_NAME: the name of the database to query
  • AUTH_TOKEN: Authentication token

Write line protocol to your InfluxDB 3 server

influxdb3 write \
  --database 
DATABASE_NAME
\
--token
AUTH_TOKEN
\
'home,room=Living\ Room temp=21.1,hum=35.9,co=0i 1641024000'
influxdb3 write \
  --database 
DATABASE_NAME
\
--token
AUTH_TOKEN
\
--file ./data.lp
cat ./data.lp | influxdb3 write \
  --database 
DATABASE_NAME
\
--token
AUTH_TOKEN

Write line protocol and accept partial writes

influxdb3 write \
  --accept-partial \
  --database 
DATABASE_NAME
\
--token
AUTH_TOKEN
\
'home,room=Living\ Room temp=21.1,hum=35.9,co=0i 1641024000'
influxdb3 write \
  --accept-partial \
  --database 
DATABASE_NAME
\
--token
AUTH_TOKEN
\
--file ./data.lp
cat ./data.lp | influxdb3 write \
  --accept-partial \
  --database 
DATABASE_NAME
\
--token
AUTH_TOKEN

Write line protocol with specific timestamp precision

By default, in CLI and HTTP API write requests, InfluxDB 3 Enterprise uses the timestamp magnitude to auto-detect the precision. To avoid any ambiguity, specify the --precision {ns|us|ms|s} option:

influxdb3 write \
  --database 
DATABASE_NAME
\
--token
AUTH_TOKEN
\
--precision s \ 'home,room=Living\ Room temp=21.1,hum=35.9,co=0i 1641024000 home,room=Kitchen temp=21.0,hum=35.9,co=0i 1641024000 home,room=Living\ Room temp=21.4,hum=35.9,co=0i 1641027600 home,room=Kitchen temp=23.0,hum=36.2,co=0i 1641027600 '

Write line protocol and immediately return a response

By default, InfluxDB 3 Enterprise waits to respond to write requests until the written data is flushed from the Write-Ahead Log (WAL) to object storage (every 1s by default). Use the --no-sync option to immediately return a response without waiting for the WAL to flush. This improves perceived write response times, but may hide certain types of write errors–for example: malformed line protocol or type conflicts.

Only use --no-sync when low write latency is more important than guaranteed data durability. Avoid using this option for critical or irreplaceable data, as it increases the risk of silent data loss.

influxdb3 write \
  --database 
DATABASE_NAME
\
--token
AUTH_TOKEN
\
--no-sync \ 'home,room=Living\ Room temp=21.1,hum=35.9,co=0i 1641024000'

Was this page helpful?

Thank you for your feedback!


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.8

Explorer 1.8 is now available with streaming data subscriptions (beta), line protocol preview, and query history & saved queries.

View Explorer 1.8 release notes

Explorer 1.8 includes new features and improvements that make it easier to ingest, explore, and manage data.

Highlights:

  • Streaming data subscriptions (beta): Stream data into Explorer from MQTT, Kafka, and AMQP sources.
  • Line protocol preview: Preview line protocol, schema, and parse errors before data is written.
  • Custom sample data: Generate custom sample datasets with line protocol and schema preview.
  • Query history and saved queries: Browse query history and save/re-run named queries.
  • Retention period management: Set, update, or clear retention periods on databases and tables.

For more details, see Explorer 1.8 release notes

InfluxDB 3.9: Performance upgrade preview

InfluxDB 3 Enterprise 3.9 includes a beta of major performance upgrades with faster single-series queries, wide-and-sparse table support, and more.

InfluxDB 3 Enterprise 3.9 includes a beta of major performance and feature updates.

Key improvements:

  • Faster single-series queries
  • Consistent resource usage
  • Wide-and-sparse table support
  • Automatic distinct value caches for reduced latency with metadata queries

Preview features are subject to breaking changes.

For more information, see:

Telegraf Enterprise now in public beta

Get early access to the Telegraf Controller and provide feedback to help shape the future of Telegraf Enterprise.

See the Blog Post

The upcoming Telegraf Enterprise offering is for organizations running Telegraf at scale and is comprised of two key components:

  • Telegraf Controller: A control plane (UI + API) that centralizes Telegraf configuration management and agent health visibility.
  • Telegraf Enterprise Support: Official support for Telegraf Controller and Telegraf plugins.

Join the Telegraf Enterprise beta to get early access to the Telegraf Controller and provide feedback to help shape the future of Telegraf Enterprise.

For more information:

Telegraf Controller v0.0.7-beta now available

Telegraf Controller v0.0.7-beta is now available with new features, improvements, bug fixes, and an important breaking change.

View the release notes
Download Telegraf Controller v0.0.7-beta

InfluxDB Docker latest tag changing to InfluxDB 3 Core

On May 27, 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