---
title: "[BETA] Get action events for a specific action set."
method: GET
path: "/api/admin/projects/{projectId}/actions/{id}/events"
tags: ["Projects"]
---

# [BETA] Get action events for a specific action set.

`GET /api/admin/projects/{projectId}/actions/{id}/events`

**Enterprise feature**

**[BETA]** This API is in beta state, which means it may change or be removed in the future.

Returns a list of action events triggered by a specific action set, identified by its id.

## Path parameters

- `projectId` string, required
- `id` string, required

## Query parameters

- `limit` string
- `offset` string

## Response `200`

#/components/schemas/actionSetEventsSchema

- ActionSetEventsSchema — A response model with a list of action set events.
  - `actionSetEvents` ActionSetEventSchema[], required — A list of action set events.
    - `id` integer, required — The action set event's ID. Action set event IDs are incrementing integers. In other words, a more recently created action set event will always have a higher ID than an older one.
    - `actionSetId` integer, required — The ID of the action set that the action set event belongs to.
    - `signalId` integer, required — The ID of the signal that triggered this action set event.
    - `createdAt` string, date-time, required — The date and time of when the action set event was created. In other words, the date and time of when the action set started executing.
    - `state` 'started' | 'success' | 'failed', required — The state of the action set event. Can be one of `started`, `success`, or `failed`.
    - `signal` SignalSchema, required — An object describing a signal.
      - `id` integer, required — The signal's ID. Signal IDs are incrementing integers. In other words, a more recently created signal will always have a higher ID than an older one.
      - `payload` object — The payload of the signal.
      - `createdAt` string, date-time, required — The date and time of when the signal was created.
      - `source` 'signal-endpoint', required — The signal source type. Should be used along with `sourceId` to uniquely identify the resource that created this signal.
      - `sourceId` integer, required — The ID of the source that created this signal. Should be used along with `source` to uniquely identify the resource that created this signal.
      - `createdBySourceTokenId` integer, nullable — The ID of the source token that created this signal. Only present if the signal was created by a signal endpoint.
    - `actionSet` object, required — The action set this action set event belongs to, where the individual actions are decorated with the respective action states.
      - `id` integer, required — The ID of the action set.
      - `project` string, required — The project that this action set belongs to.
      - `createdAt` string, date-time, required — The date and time of when the action set was created.
      - `createdByUserId` integer, required — The ID of the user that created this action set.
      - `name` string, required — The name of the action set
      - `description` string, nullable — The description of the action set
      - `actorId` integer, required — The id of the service account that will execute the action
      - `enabled` boolean — Whether this action set is enabled or not
      - `actions` ActionEventSchema[], required — The list of actions executed in sequential order when the action set was triggered, decorated with the individual action states.
        - `id` integer, required — The id of the action set
        - `createdAt` string, date-time, required — The date and time of when the action was created.
        - `createdByUserId` integer, required — The id of user that created this action set
        - `action` string, required — The name of the action to execute
        - `sortOrder` integer, required — The order in which the action should be executed
        - `executionParams` object — A map of parameters to pass to the action
        - `state` 'not started' | 'started' | 'success' | 'failed', required — The state of the action. Can be one of `not started`, `started`, `success`, or `failed`.
        - `details` string, nullable — The details of the action event, if any.
      - `match` object, required — Defines a matching rule for the signal that will trigger the action set
        - `source` 'signal-endpoint', required — Match the source of the signal
        - `sourceId` number, required — Match the source id of the signal
        - `payload` object, required — Match the payload of the signal

## Other responses

- `401` — Authorization information is missing or invalid. Provide a valid API token as the `authorization` header, e.g. `authorization:*.*.my-admin-token`.
- `403` — The provided user credentials are valid, but the user does not have the necessary permissions to perform this operation
- `404` — The requested resource was not found.

---

[API](https://skmtc.net/unleash/apis/unleash-api-3.md) · [All operations](https://skmtc.net/unleash/apis/unleash-api-3/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/unleash/unleash-api-3/versions/b2c3116e633e/schema)