CorefinityCorefinityDocs
Open the Control PanelControl Panel
Support · 6 of 12

corestack_ticket_upload_create

Upload a file for a ticket reply.

Scope writeNo secrets returned
On this page

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.

Ask for it

Prompt
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.

Inputs

filenamestringRequired

The file's name as the ticket will show it: letters, digits, spaces, dots, dashes and underscores, starting with a letter or a digit. Up to 200 characters.

size_bytesintegerRequired

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). At least 1.

Example call

tools/call
{
  "name": "corestack_ticket_upload_create",
  "arguments": {
    "filename": "checkout-error.png",
    "size_bytes": 184320
  }
}

If it is refused

ReasonWhat to do
invalid_argumentsNaming 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.
pin_refusedThe token is limited to some sites; ticket files belong to the whole company.
scope_requiredThe token lacks a scope this call needs. Open the link in the answer to add it, then call again.
rate_limitedToo many calls. Wait for the number of seconds the answer names.
temporarily_unavailableThe Control Panel could not answer just now. Nothing was started; try again shortly.
internal_errorSomething went wrong on our side. Quote the trace id to support.
  • 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 same task elsewhere

Was this helpful?
Open in ClaudeOpen in ChatGPT