Documentation

InfluxDB 3 API client libraries

Client libraries for InfluxDB 3

InfluxDB 3 client libraries are language-specific packages that work with and integrate with your application to write to and query data in InfluxDB Clustered. InfluxData and the user community maintain client libraries for developers who want to take advantage of:

  • Idioms for InfluxDB requests, responses, and errors.
  • Common patterns in a familiar programming language.
  • Faster development and less boilerplate code.

InfluxDB client libraries provide configurable batch writing of data to InfluxDB HTTP APIs. They can be used to construct line protocol data and transform data from other formats to line protocol.

InfluxDB 3 client libraries can query InfluxDB 3 using InfluxDB 3’s IOx-specific Arrow Flight protocol with gRPC. Client libraries use Flight clients to execute SQL and InfluxQL queries, request database information, and retrieve data stored in InfluxDB Clustered.

Additional features may vary among client libraries.

For specifics about a client library, see the library’s GitHub repository. InfluxDB 3 client libraries are part of the Influx Community.


Was this page helpful?

Thank you for your feedback!


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:

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