Skip to main content
POST
List integrations

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

Filter parameters for listing integrations.

p
integer
default:1

Page number, 1-based.

Required range: x >= 1
limit
integer
default:100

Page size. Defaults to 100, maximum 100.

Required range: 1 <= x <= 100
orderby
enum<string>

Sort field. Defaults to created_at; plugin_type is sorted by the underlying plugin.

Available options:
created_at,
updated_at,
name,
plugin_type,
status
category
string

Filter by category. Accepts a comma-separated list.

type
string

Deprecated. Merged into plugin_type when both are set.

plugin_type
string

Filter by integration type. Accepts a comma-separated list.

status
string

Filter by status. Accepts a comma-separated list.

name
string

Filter by integration name.

ref_ids
string[]

Filter by source reference IDs. Each value must start with c_ (channel), a_ (account) or w_.

asc
boolean

Sort ascending when true, descending when false.

is_my_team
boolean

Limit the result to integrations owned by your teams.

team_ids
integer<int64>[]

Filter by team IDs. With is_my_team, the values narrow that set further.

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 page of integrations.