Documentation

Write data to InfluxDB 3 Core

Use tools like the influxdb3 CLI, Telegraf, and InfluxDB client libraries to write time series data to InfluxDB 3 Core. line protocol is the text-based format used to write data to InfluxDB.

Tools are available to convert other formats (for example—CSV) to line protocol.

Choose the write endpoint for your workload

When creating new write workloads, use the InfluxDB HTTP API /api/v3/write_lp endpoint and client libraries.

When bringing existing v1 write workloads, use the InfluxDB 3 Core HTTP API /write endpoint.

When bringing existing v2 write workloads, use the InfluxDB 3 Core HTTP API /api/v2/write endpoint.

For Telegraf, use the InfluxDB v1.x outputs.influxdb or v2.x outputs.influxdb_v2 output plugins. See how to use Telegraf to write data.

Timestamp precision across write APIs

InfluxDB 3 Core provides multiple write endpoints for compatibility with different InfluxDB versions. The following table compares timestamp precision support across v1, v2, and v3 write APIs:

Precisionv1 (/write)v2 (/api/v2/write)v3 (/api/v3/write_lp)
Auto detection❌ No❌ Noauto (default)
Secondssssecond
Millisecondsmsmsmillisecond
Microsecondsu or µusmicrosecond
Nanosecondsnsnsnanosecond
Minutesm❌ No❌ No
Hoursh❌ No❌ No
DefaultNanosecondNanosecondAuto (guessed)

A bug currently prevents abbreviated precision values (ns, n, us, u, ms, s) from working with the /api/v3/write_lp endpoint. Use the full names (nanosecond, microsecond, millisecond, second) instead. Abbreviated values will be supported in a future release.

  • All write endpoints accept timestamps in line protocol format.
  • InfluxDB 3 Core multiplies timestamps by the appropriate precision value to convert them to nanoseconds for internal storage.
  • All timestamps are stored internally as nanoseconds regardless of the precision specified when writing.

Line protocol

All data written to InfluxDB is written using line protocol, a text-based format that lets you provide the necessary information to write a data point to InfluxDB.

Line protocol elements

In InfluxDB, a point contains a table name, one or more fields, a timestamp, and optional tags that provide metadata about the observation.

Each line of line protocol contains the following elements:

* Required
  • * table: A string that identifies the table to store the data in.
  • tag set: Comma-delimited list of key value pairs, each representing a tag. Tag keys and values are unquoted strings. Spaces, commas, and equal characters must be escaped.
  • * field set: Comma-delimited list of key value pairs, each representing a field. Field keys are unquoted strings. Spaces and commas must be escaped. Field values can be strings (quoted), floats, integers, unsigned integers, or booleans.
  • timestamp: Unix timestamp associated with the data. InfluxDB supports up to nanosecond precision. If the precision of the timestamp is not in nanoseconds, you must specify the precision when writing the data to InfluxDB.

Line protocol element parsing

  • table: Everything before the first unescaped comma before the first whitespace.
  • tag set: Key-value pairs between the first unescaped comma and the first unescaped whitespace.
  • field set: Key-value pairs between the first and second unescaped whitespaces.
  • timestamp: Integer value after the second unescaped whitespace.
  • Lines are separated by the newline character (\n). Line protocol is whitespace sensitive.

myTable,tag1=val1,tag2=val2 field1="v1",field2=1i 0000000000000000000


For schema design recommendations, see InfluxDB schema design.

Write data to InfluxDB


Was this page helpful?

Thank you for your feedback!


New in InfluxDB 3.6

Key enhancements in InfluxDB 3.6 and the InfluxDB 3 Explorer 1.4.

See the Blog Post

InfluxDB 3.6 is now available for both Core and Enterprise. This release introduces the 1.4 update to InfluxDB 3 Explorer, featuring the beta launch of Ask AI, along with new capabilities for simple startup and expanded functionality in the Processing Engine.

For more information, check out:

InfluxDB Docker latest tag changing to InfluxDB 3 Core

On February 3, 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