Create or update alert pipeline

Set the alert processing pipeline for an integration. Replaces the existing configuration entirely.

POST /alert/pipeline/upsert

Create or update alert pipeline

cURL

curl --request POST \
  --url 'https://api.flashcat.cloud/alert/pipeline/upsert?app_key=' \
  --header 'Content-Type: application/json' \
  --data '
{
  "integration_id": 10001,
  "rules": [
    {
      "kind": "severity_reset",
      "if": null,
      "settings": {
        "severity": "Warning"
      }
    }
  ]
}
'

200

{
  "request_id": "01HK8XQE3Z7JM2NTFQ5YJ8P9R4",
  "data": {}
}

Restrictions

Aspect	Value
Rate limits	1,000 requests/minute; 50 requests/second per account
Permissions	Integrations Manage (on-call)

Usage

• Maximum 50 rules per pipeline.
• Each rule has a kind (one of title_reset, description_reset, severity_reset, alert_drop, alert_inhibit), an optional if filter, and settings specific to the kind.
• The alert_inhibit kind requires the Standard license or higher.
• Every call is recorded in the account audit log. Don’t put secrets in request fields.

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 to configure.

rules · object[] · required

Rules to apply. Max 50.

Maximum array length: 50

Show child attributes

Response

200

application/json

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

Empty response body. The server returns data: null on success.