Skip to main content
POST
Update 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

Payload for updating an integration. Only the fields you send are changed.

integration_id
integer<int64>
required

Integration ID.

Required range: x >= 1
Example:

6113996590131

name
string | null

New name, 2–49 characters.

Required string length: 2 - 49
description
string | null

New description, at most 499 characters.

Maximum string length: 499
team_id
integer<int64> | null

New owning team ID; 0 clears the team assignment.

Required range: x >= 0
settings
object | null

Replacement configuration for the integration type. Sensitive entries left out, or sent back as the masked ******, keep their stored value.

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

A single integration with its full settings. Timestamps are Unix epoch seconds.