Skip to main content
POST
/
alert
/
pipeline
/
info
Get alert pipeline
curl --request POST \
  --url 'https://api.flashcat.cloud/alert/pipeline/info?app_key=' \
  --header 'Content-Type: application/json' \
  --data '
{
  "integration_id": 10001
}
'
{
  "request_id": "01HK8XQE3Z7JM2NTFQ5YJ8P9R4",
  "data": {
    "integration_id": 10001,
    "rules": [
      {
        "kind": "severity_reset",
        "if": null,
        "settings": {
          "severity": "Warning"
        }
      }
    ],
    "status": "enabled",
    "creator_id": 80011,
    "updated_by": 80011,
    "created_at": 1710000000,
    "updated_at": 1712000000
  }
}

​
Restrictions

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

​
Usage

  • Returns null data if no pipeline has been configured for the given integration.
  • Requires the caller to have access to the integration.

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
​
integration_id
integer<int64>
required

Integration ID.

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

Alert processing pipeline for an integration.