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

**Read the new ticket choices.** Read what a new support ticket can name, as the New Ticket form offers it: websites, the chosen websites' environments (website_ids), departments, priorities and the emergency notice. client_company_id picks a client company. Scope: read.

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

## When to use it

Read what a new support ticket can name, exactly as the New Ticket form offers it to the person: the websites and their
environments, the departments, the priorities (Medium is the form's default) and the notice the form shows when Emergency
is picked. An agency person also chooses the company: `companies` lists the ones the form offers, and the websites listed
are those of the token's company unless `client_company_id` names another. A ticket can name several websites and
environments: pass `website_ids` to list the environments of every one of them.

## Inputs

- `client_company_id` (integer, optional): a company from `companies`, when `chooses_company` is true.
- `website_ids` (array of integers, optional, up to 50): websites from `websites`; the answer then lists their
  environments.
- `website_id` (integer, optional): one website, as before; it is added to `website_ids`.

The answer: `chooses_company`, `companies` (null unless the person chooses a company), `company_id`, `websites`,
`website_ids` (the websites given), `website_id` (the first of them), `environments` (null until a website is given: every
environment of the websites given, each with its `website_id`), `environment_groups` (the same environments under their
website: `website_id`, `website_name`, `environments`; null until a website is given), `departments`, `priorities`
(`value`, `label`), `default_priority` and `emergency_notice` (null when none is set).

### Input schema

```json
{
  "additionalProperties": false,
  "properties": {
    "client_company_id": {
      "minimum": 1,
      "type": "integer"
    },
    "website_id": {
      "minimum": 1,
      "type": "integer"
    },
    "website_ids": {
      "items": {
        "minimum": 1,
        "type": "integer"
      },
      "maxItems": 50,
      "type": "array"
    }
  },
  "type": "object"
}
```

## Refusals

- `invalid_arguments`: the company or a website is not one the form offers this person, named in `fields` ("That website
  is not one you can raise a ticket about.", the form's words).
- `tenant_mismatch`: `client_company_id` is not a company your agency reaches.
- `pin_refused`: the token is limited to some sites; a ticket belongs to the whole company.
- The refusals every tool can answer: `scope_required`, `rate_limited`, `temporarily_unavailable`, `internal_error`
  (corestack://guides/how-this-server-works).

## Example

```json
{
  "name": "corestack_ticket_options_get",
  "arguments": {
    "website_ids": [950, 951]
  }
}
```

## Prompt

```text
Using the Corefinity MCP server, call corestack_ticket_options_get with website_ids [950,951]. (Read the new ticket choices.) Tell me what it returned.
```

## The same task elsewhere

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