---
title: "corestack_tickets_list"
url: https://docs.corefinity.com/mcp/tools/corestack_tickets_list
type: tool
last_updated: 2026-11-13
feature: support
related:
  - https://docs.corefinity.com/guides/support/raise-and-follow-a-ticket.md
---
# corestack_tickets_list

**List support tickets.** List your company's support tickets as the Tickets page does, 25 a page: those not resolved or closed unless status says otherwise (all lists every one). client_company_id lists a client company your agency reaches. Scope: read.

- Scope: `read`
- Runs as a task: no

## When to use it

List your company's support tickets, as the Tickets page lists them: open and waiting tickets by default, in the page's
order (pending first, then open and in progress by priority, then waiting, scheduled, on hold, resolved and closed;
newest first within each), 25 a page. Use it to find a ticket the person asks about, then read it with corestack_ticket_get.

## Inputs

- `status` (array of strings, optional): `all_open_with_waiting` (the default: everything not resolved or closed),
  `all_open` (pending, open, in progress and on hold), `all` (every status), or statuses: `pending`, `open`,
  `in_progress`, `waiting_on_customer`, `waiting_on_thirdparty`, `on_hold`, `scheduled`, `resolved`, `closed`.
- `priority` (array of strings, optional): `emergency`, `high`, `medium`, `low`.
- `website_ids` (array of integers, optional, up to 50): only tickets about any of these websites (ids from
  corestack_ticket_options_get).
- `website_id` (integer, optional): one website, as before; it is added to `website_ids`.
- `enterprise_env_ids` (array of integers, optional, up to 50): only tickets about any of these environments (ids from
  corestack_ticket_options_get's `environments`).
- `enterprise_env_id` (integer, optional): one environment, as before; it is added to `enterprise_env_ids`.
- `requester_id` (integer, optional): only tickets for this person (a row's `requester.id`).
- `department_id` (integer, optional): only tickets in this department.
- `client_company_id` (integer, optional): a client company your agency reaches; your own company when left out.
- `page` (integer, ≥ 1, optional): the page to read.
- `per_page` (integer, 1–100, optional): rows a page, 25 when left out.

Each row has `id`, `subject`, `status` and `status_label`, `priority` and `priority_label`, `department`, `company`,
`websites` and `environments` (every one the ticket names, `id` and `name`, by name), `website` and `environment` (the
first of each, or null), `requester` (`id`, `name`, `email`), `scheduled_for` (when a scheduled ticket comes back; null
once resolved or closed), `created_at`, `updated_at` and `url` (the ticket in the Control Panel). The answer also has
`page`, `per_page`, `total` and `last_page`.

### Input schema

```json
{
  "additionalProperties": false,
  "properties": {
    "client_company_id": {
      "minimum": 1,
      "type": "integer"
    },
    "department_id": {
      "minimum": 1,
      "type": "integer"
    },
    "enterprise_env_id": {
      "minimum": 1,
      "type": "integer"
    },
    "enterprise_env_ids": {
      "items": {
        "minimum": 1,
        "type": "integer"
      },
      "maxItems": 50,
      "type": "array"
    },
    "page": {
      "minimum": 1,
      "type": "integer"
    },
    "per_page": {
      "maximum": 100,
      "minimum": 1,
      "type": "integer"
    },
    "priority": {
      "items": {
        "enum": [
          "emergency",
          "high",
          "medium",
          "low"
        ],
        "type": "string"
      },
      "maxItems": 4,
      "type": "array"
    },
    "requester_id": {
      "minimum": 1,
      "type": "integer"
    },
    "status": {
      "items": {
        "enum": [
          "all_open",
          "all_open_with_waiting",
          "all",
          "pending",
          "open",
          "in_progress",
          "resolved",
          "closed",
          "waiting_on_customer",
          "waiting_on_thirdparty",
          "on_hold",
          "scheduled"
        ],
        "type": "string"
      },
      "maxItems": 20,
      "type": "array"
    },
    "website_id": {
      "minimum": 1,
      "type": "integer"
    },
    "website_ids": {
      "items": {
        "minimum": 1,
        "type": "integer"
      },
      "maxItems": 50,
      "type": "array"
    }
  },
  "type": "object"
}
```

## Refusals

- `pin_refused`: the token is limited to some sites. A ticket belongs to the whole company, so the step-up asks to let
  the token work everywhere in the company.
- `tenant_mismatch`: `client_company_id` is not a company your agency reaches.
- `invalid_arguments`: a status, priority, id or page value the list does not take, named in `fields`.
- The refusals every tool can answer: `scope_required`, `rate_limited`, `temporarily_unavailable`, `internal_error`
  (corestack://guides/how-this-server-works).

## Example

```json
{
  "name": "corestack_tickets_list",
  "arguments": {
    "status": ["all_open_with_waiting"],
    "priority": ["emergency", "high"],
    "per_page": 10
  }
}
```

## Prompt

```text
Using the Corefinity MCP server, call corestack_tickets_list with status ["all_open_with_waiting"], priority ["emergency","high"], per_page 10. (List support tickets.) Tell me what it returned.
```

## The same task elsewhere

- Guide: [Support tickets](https://docs.corefinity.com/guides/support/raise-and-follow-a-ticket.md)
