---
title: "Get a list of all possible cases created using Alloy Case Management."
method: GET
path: "/cases"
tags: ["Cases"]
deprecated: true
---

# Get a list of all possible cases created using Alloy Case Management.

`GET /cases`

> **Deprecated.**

<Callout type="warning" title="Deprecated Warning">
  This endpoint is deprecated in favor of using Investigations.
</Callout>

Retrieves the list of all cases, for the provided filter parameters

## Response `200`

Case

- object[]
  - `status_code` number — The standard HTTP status code for the request
  - `error` string — A nullable string, indicated what went wrong for a failed request
  - `page` number — The page itself, for the provided query
  - `pages` number — The number of overall pages, for the provided filter parameters
  - `per_page` number — The max number of items per pages, for the provided query
  - `total` number — The total number of cases, for the provided filter parameters
  - `_embedded` object — A container for the cases themselves, and their related business objects
    - `case_token` string — A unique identifier for the case itself, generated by Alloy's internal system
    - `entity_token` string — A unique identifier for the entity itself, generated by Alloy's internal system. Currently, cases can only have one entity related to it
    - `status` string — The current status of the case. This is nullable, as some cases may not have an initial status
    - `closed` boolean — This represents if the case is open or not
    - `sandbox` boolean — This represents if the case is a "real" case, or if has been used as a test. Similar to the "environment" on evaluations
    - `unread` boolean — This represents if the case has been read by a user, since it's last update
    - `created_at` number — A Unix timestamp for when the case was created
    - `updated_at` number — A Unix timestamp for when the case was last updated
    - `closed_at` number — A Unix timestamp for when the case was closed. This is null if the case is still open
    - `assigned_agent_email` string — If the case is currently assigned, this is the email of that individual
    - `assigned_agent_name` string — If the case is currently assigned, this is the full name of that individual
    - `program_name` string
    - `alerts` string[] — The tags related to the case. ALL of these tags MUST be case generating, at the time they were linked to the case. All of these tags must have the same type
    - `customer_tag_type_name` string — This is essentially the "Case Type." All tags associated to a case, must have the same type as this value tied to the case
    - `customer_tag_type_description` string — This is an extended description for the type itself
    - `is_escalated` boolean — An indicator for if the case was escalated to a different assignee. This is cleared out, upon a different assignee being chosen
    - `is_manual` boolean — Represents if the case was generated by Alloy's internal system, or some kind of manual interaction
    - `created_by_agent_email` string — If the case was manually generated, this is the full name of who took that action
    - `created_by_agent_name` string — If the case was manually generated, this is the email of who took that action
    - `_embedded` object
      - `entity` object — Relevant entity data, for the entity tied to this case
        - `name` string
        - `entity_token` string
        - `external_entity_id` string
        - `type` string
        - `_links` object
          - `self` Self — unresolved $ref
    - `_links` object
      - `self` object
        - `href` string
      - `evidences` Self — unresolved $ref
      - `works` Self — unresolved $ref

---

[API](https://skmtc.dev/alloy/apis/alloy-api.md) · [All operations](https://skmtc.dev/alloy/apis/alloy-api/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/alloy/alloy-api/revisions/405799de4d2a/schema)