URL configuration

The Infinity data source supports advanced URL configuration options including HTTP methods, custom headers, query parameters, and request bodies. Use these options to connect to any REST API or web endpoint.

Before you begin

Ensure you have the Infinity data source installed and configured
Know the API endpoint requirements (authentication, headers, body format)

Configure URL options

In the query editor, click the expand icon next to the URL field to access advanced options.

HTTP methods

Method	Description
GET	Retrieve data (default)
POST	Send data in request body
PUT	Update existing resource (requires admin configuration)
PATCH	Partial update (requires admin configuration)
DELETE	Remove resource (requires admin configuration)

Note
PUT, PATCH, and DELETE methods are considered dangerous and must be enabled by an administrator in the data source configuration.

Query parameters

Add query parameters that will be appended to the URL. Each parameter has a key and value.

Request headers

Add custom headers to send with the request. Each header has a key and value.

Request body

For POST, PUT, and PATCH requests, configure the request body:

Body type	Description
none	No request body
form-data	Multipart form data
x-www-form-urlencoded	URL-encoded form data
raw	Raw text body with content type
graphql	GraphQL query and variables

Content types for raw body:

Content type	Use case
`application/json`	JSON payloads
`application/xml`	XML payloads
`text/plain`	Plain text
`text/html`	HTML content
`application/javascript`	JavaScript

Variables in URLs

Use Grafana variables in your URL to create dynamic queries. This includes global variables and dashboard variables.

Example:

https://api.example.com/data?from=${__from:date:YYYY-MM-DD}&to=${__to:date:YYYY-MM-DD}

Result:

https://api.example.com/data?from=2024-01-01&to=2024-01-31

For more information about available variables, refer to Macros.

Secure keys in URLs

For API keys or tokens that must be included in URLs, use the secure key configuration in the data source settings instead of hardcoding them in queries.

Navigate to the data source configuration.
In the Authentication section, configure your API key.
Select whether to send the key as a Header or Query parameter.
Enter the key name and value.

The key value is stored securely and not exposed in dashboards or query logs.

Custom headers

Configure headers in two locations:

Location	Use case
Data source configuration	Headers applied to all queries
Query editor	Headers for specific queries

Default headers:

The Infinity data source automatically sets these headers:

User-Agent: Go-http-client/1.1
Content-Type: application/json (for JSON requests)

You can override these defaults in the data source configuration.

Note
Add secure or sensitive headers only in the data source configuration, not in individual queries.

Grafana metadata headers

Forward Grafana metadata to your API using macros in custom headers or query parameters.

Macro	Description
`${__org.id}`	Grafana organization ID
`${__plugin.id}`	Plugin ID
`${__plugin.version}`	Plugin version
`${__ds.uid}`	Data source UID
`${__ds.name}`	Data source name
`${__ds.id}`	Data source ID (deprecated)
`${__user.login}`	User login ID
`${__user.email}`	User email
`${__user.name}`	User display name

Warning
User macros (${__user.*}) are not available in alerts, recorded queries, or public dashboards because there is no user context in these scenarios.

Allowed hosts

Allowed hosts restrict which URLs the Infinity data source can connect to. When authentication, custom headers, or TLS certificates are configured, allowed hosts are required. If none of these features are in use and no allowed hosts are specified, all hosts are allowed by default.

To configure allowed hosts: