Get datasource detail

Retrieve full details of a single data source by its ID, including the payload configuration.

POST /monit/datasource/info

Get datasource detail

cURL

curl --request POST \
  --url 'https://api.flashcat.cloud/monit/datasource/info?app_key=' \
  --header 'Content-Type: application/json' \
  --data '{
  "id": 10
}'

200

{
  "request_id": "01HK8XQE3Z7JM2NTFQ5YJ8P9R4",
  "data": {
    "id": 10,
    "account_id": 10023,
    "type_ident": "prometheus",
    "name": "Prometheus Prod",
    "enabled": true,
    "note": "Production Prometheus",
    "address": "http://prometheus.example.com:9090",
    "payload": {
      "prometheus": {
        "basic_auth_enabled": false,
        "basic_auth_username": "",
        "basic_auth_password": "",
        "tls_skip_verify": false
      }
    },
    "edge_cluster_name": "default",
    "updated_at": 1712000000
  }
}

Restrictions

Aspect	Value
Rate limits	1,000 requests/minute; 50 requests/second per account
Permissions	Datasources Read (monit)

Authorizations

app_key · string · query · required

App key issued from the Flashduty console under Account → APP Keys. Required on every public API call. Keep it secret — it grants the same access as the owning account.

Body

application/json

Request with a single numeric ID.

id · integer<uint64> · required

Resource ID.

Response

200

application/json

Success

Success response envelope. On every 2xx response, request_id identifies the call (also mirrored in the Flashcat-Request-Id header) and data holds the endpoint-specific payload. Failure responses use a different shape — see ErrorResponse.

request_id · string · required

Unique ID for this request. Mirrored in the Flashcat-Request-Id response header. Include it when reporting issues.

Example:

"01HK8XQE3Z7JM2NTFQ5YJ8P9R4"

data · object · required

A monitoring datasource.

Show child attributes