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

​
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 listing routing rules across multiple integrations.

​
integration_ids
integer<int64>[]
required

Integration IDs to fetch routing rules for.

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

Response wrapper for the routing rule list.