Documentation function is experimental and subject to change at any time. makes an http request.


Experimental is deprecated in favor of

The returned response contains the following properties:

  • statusCode: HTTP status code returned from the request.
  • body: Contents of the request. A maximum size of 100MB will be read from the response body.
  • headers: Headers present on the response.
  • duration: Duration of request.
Function type signature
    method: string,
    url: string,
    ?body: bytes,
    ?config: {A with timeout: duration, insecureSkipVerify: bool},
    ?headers: [string:string],
    ?params: [string:[string]],
) => {statusCode: int, headers: [string:string], duration: duration, body: bytes}

For more information, see Function type signatures.



(Required) method of the http request. Supported methods: DELETE, GET, HEAD, PATCH, POST, PUT.


(Required) URL to request. This should not include any query parameters.


Set of key value pairs to add to the URL as query parameters. Query parameters will be URL encoded. All values for a key will be appended to the query.


Set of key values pairs to include on the request.


Data to send with the request.


Set of options to control how the request should be performed.


Make a GET request

import "experimental/http/requests"

response = "", method: "GET")

requests.peek(response: response)

Make a GET request that needs authorization

import "experimental/http/requests"
import "influxdata/influxdb/secrets"

token = secrets.get(key: "TOKEN")

response =
        method: "GET",
        url: "",
        headers: ["Authorization": "token ${token}"],

requests.peek(response: response)

Make a GET request with query parameters

import "experimental/http/requests"

response = "GET", url: "", params: ["start": ["100"]])

requests.peek(response: response)

Was this page helpful?

Thank you for your feedback!

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: