Documentation

/write 1.x compatibility API

This page documents an earlier version of InfluxDB OSS. InfluxDB 3 Core is the latest stable version.

The /write 1.x compatibility endpoint writes data to InfluxDB Cloud and InfluxDB OSS 2.7 using patterns from the InfluxDB 1.x /write API endpoint. Use the POST request method to write line protocol to the /write endpoint.

POST http://localhost:8086/write

Authentication

Use one of the following authentication methods:

  • token authentication
  • basic authentication with username and password
  • query string authentication with username and password

For more information, see Authentication.

Request body

Include your line protocol in the request body. Binary encode the line protocol to prevent unintended formatting. The examples below use the curl --data-binary flag to binary encode the line protocol.

Query string parameters

u

(Optional) The 1.x username to authenticate the request. See query string authentication.

p

(Optional) The 1.x password to authenticate the request. See query string authentication.

db

(Required) The database to write data to. This is mapped to an InfluxDB bucket. See Database and retention policy mapping.

rp

The retention policy to write data to. This is mapped to an InfluxDB bucket. See Database and retention policy mapping.

precision

The precision of Unix timestamps in the line protocol. Default is nanosconds (ns). The following precisions are available:

  • ns - nanoseconds
  • u or µ - microseconds
  • ms - milliseconds
  • s - seconds
  • m - minutes
  • h - hours

Write examples

Write data using basic authentication
curl --request POST http://localhost:8086/write?db=
DATABASE_NAME
\
--user "
USERNAME
:
PASSWORD_OR_TOKEN
"
\
--data-binary "measurement,host=host1 field1=2i,field2=2.0 1577836800000000000"
Write data using token authentication
curl --request POST http://localhost:8086/write?db=
DATABASE_NAME
\
--header "Authorization: Token
API_TOKEN
"
\
--data-binary "measurement,host=host1 field1=2i,field2=2.0 1577836800000000000"
Write data to a non-default retention policy
curl --request POST "http://localhost:8086/write?db=
DATABASE_NAME
&rp=RETENTION_POLICY"
\
--header "Authorization: Token
API_TOKEN
"
\
--data-binary "measurement,host=host1 field1=2i,field2=2.0 1577836800000000000"
Write multiple lines of line protocol
curl --request POST http://localhost:8086/write?db=
DATABASE_NAME
\
--header "Authorization: Token
API_TOKEN
"
\
--data-binary "measurement,host=host1 field1=2i,field2=2.0 1577836800000000000 measurement,host=host2 field1=14i,field2=12.7 1577836800000000000 measurement,host=host3 field1=5i,field2=6.8 1577836800000000000"
Write data with millisecond Unix timestamps
curl --request POST "http://localhost:8086/write?db=
DATABASE_NAME
&precision=ms"
\
--header "Authorization: Token
API_TOKEN
"
\
--data-binary "measurement,host=host1 field1=2i,field2=2.0 1577836800000"
Use curl to write data from a file
curl --request POST http://localhost:8086/write?db=
DATABASE_NAME
\
--header "Authorization: Token
API_TOKEN
"
\
--data-binary @path/to/line-protocol.txt

Replace the following:


Was this page helpful?

Thank you for your feedback!


New in InfluxDB 3.5

Key enhancements in InfluxDB 3.5 and the InfluxDB 3 Explorer 1.3.

See the Blog Post

InfluxDB 3.5 is now available for both Core and Enterprise, introducing custom plugin repository support, enhanced operational visibility with queryable CLI parameters and manual node management, stronger security controls, and general performance improvements.

InfluxDB 3 Explorer 1.3 brings powerful new capabilities including Dashboards (beta) for saving and organizing your favorite queries, and cache querying for instant access to Last Value and Distinct Value caches—making Explorer a more comprehensive workspace for time series monitoring and analysis.

For more information, check out:

InfluxDB Docker latest tag changing to InfluxDB 3 Core

On November 3, 2025, 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