Skip to main content
POST
Get routing rule detail

Restrictions

Usage

  • When the integration has no routing rule, the response carries only request_id, with no data field.
  • A channel-exclusive or unknown integration_id returns 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 retrieving the routing rule of one integration.

integration_id
integer<int64>
required

Shared integration ID, greater than 0; obtain it from POST /integration/list.

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

Routing rule of a shared integration. Alerts are evaluated against cases in order; when no case yields a channel, default is used.