Skip to main content
POST
List routing rules

Restrictions

Usage

  • Integrations without a routing rule are omitted from items.
  • Every ID must be an existing shared integration; a single unknown or channel-exclusive ID fails the whole call with InvalidParameter.

Authorizations

app_key
string
query
required

APP Key created in the Flashduty console under My → APP Key. Send it as the app_key query parameter or in the Fd-App-Key request header. Its effective access is the intersection of the key's permission scope and the creator's current role permissions. Keep it secret.

Body

application/json

Parameters for listing routing rules across multiple integrations.

integration_ids
integer<int64>[]
required

Shared integration IDs to fetch routing rules for, at least one; obtain them from POST /integration/list.

Minimum array length: 1

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

Response wrapper for the routing rule list.