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 3 Enterprise. 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 the Flight protocol to execute SQL and InfluxQL queries, request database information, and retrieve data stored in InfluxDB 3 Enterprise.

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!


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