Skip to main content
POST
/
api
/
v1
/
tenant
/
telemetry
Telemetry data from Prometheus. If start and end is set to millis, histogram response will 'extends bounds'
curl --request POST \
  --url https://api.example.com/api/v1/tenant/telemetry \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '
{
  "metric": "haas_interceptor_messages_succeeded_total",
  "start": "-1d",
  "step": "1h",
  "tags": {
    "chain": [
      "ethereum",
      "vechain"
    ],
    "type": [
      "TRANSACTION"
    ]
  },
  "end": "now"
}
'
{
  "data": [
    {
      "ts": 123,
      "bucket": {}
    }
  ]
}

Authorizations

​
Authorization
string
header
required

Authentication

Body

application/json
​
metric
string
required

Metric for the MetricsQL expression

Minimum string length: 1
Example:

"haas_interceptor_messages_succeeded_total"

​
start
string
required

Starting timestamp of the time range for query evaluation, string date math or ms. Example: -1d, 1725656400000

Example:

"-1d"

​
step
string
required

The interval between data points

Example:

"1h"

​
tags
object

Tags of the MetricsQL expression

Example:
{
  "chain": ["ethereum", "vechain"],
  "type": ["TRANSACTION"]
}
​
end
string

Ending timestamp of the time range for query evaluation, string date math or ms. If the end isn’t set, then the end is automatically set to the current time. Example: now, 1726229909672

Example:

"now"

Response

200 - application/json

OK

​
data
object[]

Response data