Skip to main content
POST
List Automation runs

Restrictions

Usage

  • Run history is visible only when the caller can manage the rule: the personal rule owner; for team rules, an account admin or a member of the rule’s team.

Authorizations

app_key
string
query
required

App key issued from the Flashduty console. Required on every public API call. Keep it secret — it grants the same access as the owning account.

Body

application/json
rule_id
string
required

Target rule ID.

p
integer
default:1

Page number, 1-based.

limit
integer
default:20

Page size.

Required range: x <= 100
status
enum<string>

Run status filter.

Available options:
queued,
running,
retrying,
succeeded,
partial,
failed,
skipped,
abandoned
trigger_kind
enum<string>

Trigger kind filter.

Available options:
schedule,
debug,
manual,
http_post,
oncall_incident
started_after_ms
integer<int64>

Start-time lower bound, Unix milliseconds.

started_before_ms
integer<int64>

Start-time upper bound, Unix milliseconds.

Response

Success

Standard response envelope used by every Flashduty public API. On success data contains the endpoint-specific payload and error is absent. On failure error is present and data is absent. request_id is always present and is also mirrored in the Flashcat-Request-Id response header.

request_id
string
required

Unique ID for this request. Mirrored in the Flashcat-Request-Id header. Include it when reporting issues.

Example:

"01HK8XQE3Z7JM2NTFQ5YJ8P9R4"

error
object

Error payload inside the response envelope. Present only on non-2xx responses.

data
object

Endpoint-specific payload. See each operation's 200 response schema.