---
title: "[BETA] List action sets."
method: GET
path: "/api/admin/projects/{projectId}/actions"
tags: ["Projects"]
---

# [BETA] List action sets.

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

**Enterprise feature**

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

Returns the list of all action sets.

## Path parameters

- `projectId` string, required

## Response `200`

actionsListSchema

- ActionsListSchema — A response model with a list of action sets.
  - `actions` ActionsSchema[], required — A list of action sets.
    - `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` ActionSchema[], required — The list of actions to execute in sequential order when the action set is triggered.
      - `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
    - `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

---

[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)