Skip to main content
POST
List Automation runs

Restrictions

Usage

  • Manage rights: a personal rule (team_id=0) can be managed only by its owner; a team rule only by members of that team. Account owners and admins get no exemption and must join the team. Others get 403.
  • Run history is kept for 180 days; earlier started_after_ms values are raised to that floor.
  • Results are sorted by started_at descending.
  • For runs that executed in an IM chat (execution_place=im), session_id, joined_session_id, and result_json are withheld.

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
rule_id
string
required

Target rule ID, from the list returned by POST /safari/automation/rule/list.

p
integer
default:1

Page number, 1-based.

limit
integer
default:20

Page size. Values below 1 fall back to 20.

status
enum<string>

Run status filter: queued, running, retrying, succeeded, partial (partially succeeded), failed, skipped (e.g. rule or trigger no longer valid), abandoned (stale run terminated by the system), blocked (terminal; produced output but a connector is waiting on a human authorization); omit for no filter.

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

Trigger filter: schedule schedule trigger, debug debug run, manual manual run, http_post HTTP POST trigger, oncall_incident On-call incident trigger, war_room_created war room trigger; omit for no filter.

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

Start-time lower bound, Unix milliseconds. Values below the 180-day run-history retention floor are clamped to it (that floor is also the default when omitted).

Required range: x >= 0
started_before_ms
integer<int64>

Start-time upper bound, Unix milliseconds. Must be greater than or equal to the effective started_after_ms; a value below the retention floor yields an empty result.

Required range: x >= 0

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

Operation-specific payload, documented in each operation's 200 response. Operations without a payload return {} or omit data entirely.