Skip to main content
POST
/
route
/
info
Get routing rule detail
curl --request POST \
  --url 'https://api.flashcat.cloud/route/info?app_key=' \
  --header 'Content-Type: application/json' \
  --data '
{
  "integration_id": 6113996590131
}
'
{
  "request_id": "01HK8XQE3Z7JM2NTFQ5YJ8P9R4",
  "data": {
    "integration_id": 6113996590131,
    "cases": [
      {
        "if": [
          {
            "key": "labels.check",
            "oper": "IN",
            "vals": [
              "cpu.idle<20%"
            ]
          }
        ],
        "channel_ids": [
          2533748993131
        ],
        "fallthrough": false,
        "routing_mode": "standard"
      },
      {
        "if": [
          {
            "key": "severity",
            "oper": "IN",
            "vals": [
              "Warning"
            ]
          }
        ],
        "channel_ids": null,
        "fallthrough": false,
        "routing_mode": "name_mapping",
        "name_mapping_label": "labels.service"
      }
    ],
    "default": {
      "channel_ids": [
        3521074710131
      ]
    },
    "status": "enabled",
    "version": 6,
    "updated_by": 3790925372131,
    "creator_id": 3790925372131,
    "created_at": 1774606136,
    "updated_at": 1774606136
  }
}

Documentation Index

Fetch the complete documentation index at: https://docs.flashcat.cloud/llms.txt

Use this file to discover all available pages before exploring further.

Restrictions

AspectValue
Rate limits1,000 requests/minute; 50 requests/second per account
PermissionsIntegrations Read (on-call) or Integrations Manage (on-call)

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

Parameters for retrieving the routing rule of one integration.

integration_id
integer<int64>
required

Integration ID. Must be greater than 0.

Response

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

Routing rule of an integration. Alerts are evaluated against cases in order; unmatched alerts fall through to default. Returns null when the integration has no configured rule.