Skip to main content
POST
Upsert routing rule

Restrictions

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 creating or updating the routing rule of an integration. The handler creates a rule when none exists for the integration, otherwise it overwrites the existing one. At least one of cases or default must be provided.

integration_id
integer<int64>
required

Integration the rule belongs to.

cases
object[]

Ordered list of case branches. Cases are evaluated top to bottom.

sections
object[]

Optional sections that group consecutive cases for display.

default
object

Default branch used when no case matches (or all matched cases yield no valid channels).

version
integer<int64>

Expected current version for optimistic concurrency control. Pass the value returned by the latest read.

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

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