Write data with the InfluxDB API

Write data into InfluxDB using the command line interface, client libraries, and plugins for common data formats such as Graphite.

Note: The following examples use curl, a command line tool that transfers data using URLs. Learn the basics of curl with the HTTP Scripting Guide.

Create a database using the InfluxDB API

To create a database send a POST request to the /query endpoint and set the URL parameter q to CREATE DATABASE <new_database_name>. The example below sends a request to InfluxDB running on localhost and creates the mydb database:

curl -i -XPOST http://localhost:8086/query --data-urlencode "q=CREATE DATABASE mydb"

Write data using the InfluxDB API

The InfluxDB API is the primary means of writing data into InfluxDB.

• To write to a database using the InfluxDB 1.8 API, send POST requests to the /write endpoint. For example, to write a single point to the mydb database. The data consists of the measurement cpu_load_short, the tag keys host and region with the tag values server01 and us-west, the field key value with a field value of 0.64, and the timestamp 1434055562000000000.

curl -i -XPOST 'http://localhost:8086/write?db=mydb'
--data-binary 'cpu_load_short,host=server01,region=us-west value=0.64 1434055562000000000'

• To write to a database using the InfluxDB 2.0 API (compatible with InfluxDB 1.8+), send POST requests to the /api/v2/write endpoint:

curl -i -XPOST 'http://localhost:8086/api/v2/write?bucket=db/rp&precision=ns' \
  --header 'Authorization: Token username:password' \
  --data-raw 'cpu_load_short,host=server01,region=us-west value=0.64 1434055562000000000'

When writing points, you must specify an existing database in the db query parameter. Points will be written to db’s default retention policy if you do not supply a retention policy via the rp query parameter. See the InfluxDB API Reference documentation for a complete list of the available query parameters.

The body of the POST or InfluxDB line protocol contains the time series data that you want to store. Data includes:

• Measurement (required)
• Tags: Strictly speaking, tags are optional but most series include tags to differentiate data sources and to make querying both easy and efficient. Both tag keys and tag values are strings.
• Fields (required): Field keys are required and are always strings, and, by default, field values are floats.
• Timestamp: Supplied at the end of the line in Unix time in nanoseconds since January 1, 1970 UTC - is optional. If you do not specify a timestamp, InfluxDB uses the server’s local nanosecond timestamp in Unix epoch. Time in InfluxDB is in UTC format by default.

Note: Avoid using the following reserved keys: _field, _measurement, and time. If reserved keys are included as a tag or field key, the associated point is discarded.

Configure gzip compression

InfluxDB supports gzip compression. To reduce network traffic, consider the following options:

• To accept compressed data from InfluxDB, add the Accept-Encoding: gzip header to InfluxDB API requests.

• To compress data before sending it to InfluxDB, add the Content-Encoding: gzip header to InfluxDB API requests.

For details about enabling gzip for client libraries, see your client library documentation.

Enable gzip compression in the Telegraf InfluxDB output plugin

• In the Telegraf configuration file (telegraf.conf), under [[outputs.influxdb]], change content_encoding = "identity" (default) to content_encoding = "gzip"

Note Writes to InfluxDB 2.x [[outputs.influxdb_v2]] are configured to compress content in gzip format by default.

Writing multiple points

Post multiple points to multiple series at the same time by separating each point with a new line. Batching points in this manner results in much higher performance.

The following example writes three points to the database mydb. The first point belongs to the series with the measurement cpu_load_short and tag set host=server02 and has the server’s local timestamp. The second point belongs to the series with the measurement cpu_load_short and tag set host=server02,region=us-west and has the specified timestamp 1422568543702900257. The third point has the same specified timestamp as the second point, but it is written to the series with the measurement cpu_load_short and tag set direction=in,host=server01,region=us-west.

curl -i -XPOST 'http://localhost:8086/write?db=mydb' --data-binary 'cpu_load_short,host=server02 value=0.67
cpu_load_short,host=server02,region=us-west value=0.55 1422568543702900257
cpu_load_short,direction=in,host=server01,region=us-west value=2.0 1422568543702900257'

Writing points from a file

Write points from a file by passing @filename to curl. The data in the file should follow the InfluxDB line protocol syntax.

Example of a properly-formatted file (cpu_data.txt):

cpu_load_short,host=server02 value=0.67
cpu_load_short,host=server02,region=us-west value=0.55 1422568543702900257
cpu_load_short,direction=in,host=server01,region=us-west value=2.0 1422568543702900257

Write the data in cpu_data.txt to the mydb database with:

curl -i -XPOST 'http://localhost:8086/write?db=mydb' --data-binary @cpu_data.txt

Note: If your data file has more than 5,000 points, it may be necessary to split that file into several files in order to write your data in batches to InfluxDB. By default, the HTTP request times out after five seconds. InfluxDB will still attempt to write the points after that time out but there will be no confirmation that they were successfully written.

Schemaless Design

InfluxDB is a schemaless database. You can add new measurements, tags, and fields at any time. Note that if you attempt to write data with a different type than previously used (for example, writing a string to a field that previously accepted integers), InfluxDB will reject those data.

A note on REST

InfluxDB uses HTTP solely as a convenient and widely supported data transfer protocol.

Modern web APIs have settled on REST because it addresses a common need. As the number of endpoints grows the need for an organizing system becomes pressing. REST is the industry agreed style for organizing large numbers of endpoints. This consistency is good for those developing and consuming the API: everyone involved knows what to expect.

REST, however, is a convention. InfluxDB makes do with three API endpoints. This simple, easy to understand system uses HTTP as a transfer method for InfluxQL. The InfluxDB API makes no attempt to be RESTful.

HTTP response summary

• 2xx: If your write request received HTTP 204 No Content, it was a success!
• 4xx: InfluxDB could not understand the request.
• 5xx: The system is overloaded or significantly impaired.

Examples

Writing a float to a field that previously accepted booleans

curl -i -XPOST 'http://localhost:8086/write?db=hamlet' --data-binary 'tobeornottobe booleanonly=true'

curl -i -XPOST 'http://localhost:8086/write?db=hamlet' --data-binary 'tobeornottobe booleanonly=5'

returns:

HTTP/1.1 400 Bad Request
Content-Type: application/json
Request-Id: [...]
X-Influxdb-Version: 1.8.10
Date: Wed, 01 Mar 2017 19:38:01 GMT
Content-Length: 150

{"error":"field type conflict: input field \"booleanonly\" on measurement \"tobeornottobe\" is type float, already exists as type boolean dropped=1"}

Writing a point to a database that doesn’t exist

curl -i -XPOST 'http://localhost:8086/write?db=atlantis' --data-binary 'liters value=10'

returns:

HTTP/1.1 404 Not Found
Content-Type: application/json
Request-Id: [...]
X-Influxdb-Version: 1.8.10
Date: Wed, 01 Mar 2017 19:38:35 GMT
Content-Length: 45

{"error":"database not found: \"atlantis\""}

Next steps

Now that you know how to write data with the InfluxDB API, discover how to query them with the Querying data guide! For more information about writing data with the InfluxDB API, please see the InfluxDB API reference.