Documentation

InfluxDB API client library tutorials

Follow step-by-step tutorials to build an Internet-of-Things (IoT) application with InfluxData client libraries and your favorite framework or language. 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.

In these tutorials, you’ll use the InfluxDB API and client libraries to build a modern application, and learn the following:

  • InfluxDB core concepts.
  • How the application interacts with devices and InfluxDB.
  • How to authenticate apps and devices to the API.
  • How to install a client library.
  • How to write and query data in InfluxDB.
  • How to use the InfluxData UI libraries to format data and create visualizations.
api

Was this page helpful?

Thank you for your feedback!


Introducing InfluxDB Clustered

A highly available InfluxDB 3.0 cluster on your own infrastructure.

InfluxDB Clustered is a highly available InfluxDB 3.0 cluster built for high write and query workloads on your own infrastructure.

InfluxDB Clustered is currently in limited availability and is only available to a limited group of InfluxData customers. If interested in being part of the limited access group, please contact the InfluxData Sales team.

Learn more
Contact InfluxData Sales

The future of Flux

Flux is going into maintenance mode. You can continue using it as you currently are without any changes to your code.

Flux is going into maintenance mode and will not be supported in InfluxDB 3.0. This was a decision based on the broad demand for SQL and the continued growth and adoption of InfluxQL. We are continuing to support Flux for users in 1.x and 2.x so you can continue using it with no changes to your code. If you are interested in transitioning to InfluxDB 3.0 and want to future-proof your code, we suggest using InfluxQL.

For information about the future of Flux, see the following: