Skip to main content
POST
Enable public integration

Restrictions

Usage

  • Enabling an integration resumes its scheduled pull task and heartbeat, and requires the integration type to be available on the current plan.
  • Enabling an integration that is already enabled succeeds without change; the same holds for disabling a disabled one.
  • Every call is recorded in the account audit log.
  • These APIs manage public (account-level) integrations only, not channel-owned dedicated integrations.
  • Write access also requires object permission: the account owner, an administrator, the creator, or a member of the assigned team; with no team, members with Integrations Manage may operate. Read-only integrations cannot be changed.

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

Identifies the integration to act on.

integration_id
integer<int64>
required

ID of a public integration, returned by POST /integration/list. An unknown ID or a channel-owned integration returns ResourceNotFound.

Required range: x >= 1
Example:

6113996590131

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

An empty object. Returned as the data payload by operations whose success signal is simply the absence of an error.