Workflows
List an ingress trigger's requests
Read the requests to an ingress (inbound URL) trigger, newest first.
GET
List an ingress trigger's recent requests
The reference panel describes the current v3 operation. The notes below describe its v2 compatibility API. Follow the v3 request schema for current calls: v3 can move identifiers from the body or query into the URL. Keep the v2 method, path, and payload together when using the compatibility API.
v2 compatibility notes
GET /api/v2/workflows/listIngressInvocations?triggerId=<id>[&limit=<1-20>&cursor=<cursor>] lists the requests to an ingress trigger, newest first, a page at a time: the outcome, status code, reason and the run each request launched.
Authentication
External App credential or platform API key, or a Personal key. Requires permissionworkflows:read at the trigger’s workflow’s home and at the trigger’s own org unit, the rule of getTrigger.
An unknown or malformed id, a trigger the caller cannot read, and a trigger that is not an ingress trigger all return the same 404. limit is 1 to 20 (default 20; a larger value is 400 too_big). While meta.hasMore is true, pass meta.nextCursor as cursor (with the same triggerId) for the next page. A page may hold fewer requests than limit while more remain; the list never answers meta.partial. The log never holds a request body, header, address or dedupe key, and requests are kept 7 days.
