Create a reply to a support ticket
Posts a reply the customer and Corefinity both read: body in Markdown, up to 20 files, or both. Everyone following the ticket is told, and a ticket that was waiting on you, resolved or closed goes back to Corefinity. Send files as attachments[] in a multipart form, or send each ahead through an upload and name its upload_id in upload_ids; an internal note is refused.
Path parameters
The number of a ticket. Digits only. At least 1.
Body
The reply, in Markdown.
Files sent ahead, by their upload_id. Each is attached once, so an id named twice is refused. With the files of a multipart form, at most 20 in one reply.
Returns
201 The reply was posted.
Fields of the 201 answer
Fields of each item
The file for your token: the download endpoint.
At least 1.
Bytes.
Opens the file in the Control Panel when you are signed in.
The reply as the page shows it.
The same words as plain text.
Format: date-time.
At least 1.
The ticket as the list shows it after the reply. A ticket as the list shows it.
Fields
The company the ticket is for.
Format: date-time.
The department the ticket is in.
The first of environments, or null.
Every environment the ticket is about.
Fields of each item
At least 1.
At least 1.
emergencyhighmediumlowWho the ticket is for.
When a scheduled ticket comes back to Corefinity's queue. Null once a ticket is resolved or closed. Format: date-time.
pendingopenin_progresswaiting_on_customerwaiting_on_thirdpartyon_holdscheduledresolvedclosedFormat: date-time.
The ticket in the Control Panel.
The first of websites, or null.
Every website the ticket is about.
Fields of each item
At least 1.
If it is refused
| Status | Reason | What to do |
|---|---|---|
401 | none | Send a valid token as Authorization: Bearer <token>. |
403 | scope_required | Use a token with the scope named in scope. |
404 | none | Check the id. You see only what your account can reach. |
422 | invalid | Fix the field named in field; errors says why. |
429 | rate_limited | Wait for the seconds in Retry-After. |
Reasons are listed by name in Errors and refusals.
The same task elsewhere
curl -X POST https://manage.corefinity.com/api/support/tickets/48210/replies \
-H "Authorization: Bearer $COREFINITY_TOKEN" \
-H "Accept: application/json" \
-H "Content-Type: application/json" \
-d '{
"body": "The error stopped after we cleared the cache."
}'use Illuminate\Support\Facades\Http;
$response = Http::withToken(env('COREFINITY_TOKEN'))
->acceptJson()
->post('https://manage.corefinity.com/api/support/tickets/48210/replies', [
'body' => 'The error stopped after we cleared the cache.',
]);
$data = $response->json();const res = await fetch('https://manage.corefinity.com/api/support/tickets/48210/replies', {
method: 'POST',
headers: {
Authorization: `Bearer ${process.env.COREFINITY_TOKEN}`,
Accept: 'application/json',
'Content-Type': 'application/json',
},
body: JSON.stringify({
body: 'The error stopped after we cleared the cache.',
}),
});
// An answer with no body (204) has nothing to parse.
const text = await res.text();
const data = text && JSON.parse(text);import os
import requests
res = requests.post(
"https://manage.corefinity.com/api/support/tickets/48210/replies",
headers={
"Authorization": f"Bearer {os.environ['COREFINITY_TOKEN']}",
"Accept": "application/json",
},
json={
"body": "The error stopped after we cleared the cache.",
},
)
data = res.json() if res.content else None{
"attachments": [],
"author": {
"email": "[email protected]",
"id": 2041,
"name": "Eleanor Finch"
},
"body_html": "\n<p>The error stopped after we cleared the cache.</p>\n",
"body_text": "The error stopped after we cleared the cache.",
"created_at": "2026-11-03T16:40:11Z",
"id": 90312,
"ticket": {
"company": {
"id": 1204,
"name": "Harbour & Finch"
},
"created_at": "2026-11-02T08:14:03Z",
"department": {
"id": 21,
"name": "Support"
},
"environment": {
"id": 1311,
"name": "Production"
},
"environments": [
{
"id": 1311,
"name": "Production"
}
],
"id": 48210,
"priority": "high",
"priority_label": "High",
"requester": {
"email": "[email protected]",
"id": 2041,
"name": "Eleanor Finch"
},
"scheduled_for": null,
"status": "open",
"status_label": "Open",
"subject": "Checkout returns a 502",
"updated_at": "2026-11-03T16:40:11Z",
"url": "https://manage.corefinity.com/resources/tickets/48210",
"website": {
"id": 1310,
"name": "Harbour & Finch trade"
},
"websites": [
{
"id": 1310,
"name": "Harbour & Finch trade"
}
]
}
}{
"message": "Unauthenticated."
}{
"code": "scope_required",
"message": "This access token does not have the destructive scope this needs. Use a token with the destructive scope.",
"reason": "scope_required",
"scope": "destructive"
}{
"message": "Not found."
}{
"code": "invalid",
"errors": {
"attachments": [
"The attachments field is required when none of body / upload ids are present."
],
"body": [
"The body field is required when none of attachments / upload ids are present."
]
},
"field": "body",
"message": "The body field is required when none of attachments / upload ids are present. (and 1 more error)",
"reason": "invalid"
}{
"code": "rate_limited",
"message": "Too many requests. Try again in 60 seconds.",
"reason": "rate_limited",
"retry_after_seconds": 60
}Try it is off for this endpointIt sends email to real people. Copy the request and run it yourself when you are sure.