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

**Upload a file for a ticket reply.** Open an upload slot for one file (a screenshot, a log) to attach to a ticket reply. PUT the whole file to url with curl, then pass upload_id in upload_ids to corestack_ticket_reply. The url is shown only now and works for an hour; the file is deleted after a day if no reply takes it. Scope: write.

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

## When to use it

Attach a file (a screenshot, a log, an export) to a support ticket reply. Open an upload slot with this tool, send the
whole file to the `url` it answers in one `PUT` (the `lines.one_request` curl line), then pass the `upload_id` in
`upload_ids` to corestack_ticket_reply. The `url` is shown only in this answer and works for an hour; a file no reply takes
is deleted after a day (`expires_at`). Each call opens a new slot, for one file.

## Inputs

- `filename` (string, 1 to 200 characters, required): the file's name as the ticket will show it: letters, digits,
  spaces, dots, dashes and underscores, starting with a letter or a digit.
- `size_bytes` (integer, ≥ 1, required): the file's exact size. The `PUT` must send exactly this many bytes, and no more
  than `max_bytes` (the same limit as a file attached on the ticket page).

### Input schema

```json
{
  "additionalProperties": false,
  "properties": {
    "filename": {
      "description": "Letters, digits, spaces, dots, dashes and underscores.",
      "maxLength": 200,
      "minLength": 1,
      "type": "string"
    },
    "size_bytes": {
      "minimum": 1,
      "type": "integer"
    }
  },
  "required": [
    "filename",
    "size_bytes"
  ],
  "type": "object"
}
```

## Refusals

- `invalid_arguments` naming `filename`: a name with other characters, a name with no extension, or a type the ticket
  page does not accept either (scripts and programs, such as `.php`, `.exe` or `.sh`). The `PUT` then checks the
  bytes agree with the name.
- `invalid_arguments` naming `size_bytes`: larger than the ticket page accepts.
- `pin_refused`: the token is limited to some sites; ticket files belong to the whole company.
- The `PUT` itself answers `409` with `already_received` if the slot has its file already, `422` if the file is not
  `size_bytes` long, is sent without its `Content-Length` (curl's `--upload-file` sends it), is a type that is not
  allowed, or is not the type its name claims (the bytes are sniffed, so a script called `photo.jpg` is refused),
  `403` if the url was changed or has expired, and `404` once the slot is past its day.
- The refusals every tool can answer: `invalid_arguments`, `scope_required`, `rate_limited`, `temporarily_unavailable`,
  `internal_error` (corestack://guides/how-this-server-works).

## Example

```json
{
  "name": "corestack_ticket_upload_create",
  "arguments": {
    "filename": "checkout-error.png",
    "size_bytes": 184320
  }
}
```

## Prompt

```text
Using the Corefinity MCP server, call corestack_ticket_upload_create with filename checkout-error.png, size_bytes 184320. (Upload a file for a ticket reply.) Tell me what it returned.
```

## The same task elsewhere

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