List Automation rules
List Automation rules visible to the caller.
Restrictions
Usage
allreturns your personal rules plus team rules you can access.- Account admins see all team rules in list results, but not other users’ personal rules.
team_idsnarrows the visible set and never expands access.
Authorizations
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
List Automation rules visible to the caller. all includes the caller's personal rules plus accessible team rules; account admins do not see other users' personal rules in list results.
Page number, 1-based.
Page size.
x <= 100Scope filter: all (own personal + accessible team rules), personal, or team; default all.
all, personal, team Filter to these team IDs; this narrows results and does not expand access.
Compatibility field; when scope is empty and this is false, behaves like team scope.
Filter by enabled status.
Filter by name keyword.
64Response
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.
Unique ID for this request. Mirrored in the Flashcat-Request-Id header. Include it when reporting issues.
"01HK8XQE3Z7JM2NTFQ5YJ8P9R4"
Error payload inside the response envelope. Present only on non-2xx responses.
Endpoint-specific payload. See each operation's 200 response schema.