Skip to main content
POST
Reply to a checklist item escalation
Replies to an open escalation on a public checklist item, with an optional message body and optional file attachments, on a filing filed by your subtree. Moves the escalation to waiting on Turris. Returns the filing with the reply in place. Send it as multipart/form-data: sourceCategoryId, sourceTaskId, and an optional body, plus zero or more files parts. At least one of body or files is expected. A plain application/json body carrying just sourceCategoryId, sourceTaskId, and body also works, with no files key.

Identifying the checklist item

sourceCategoryId and sourceTaskId come from the filingโ€™s own checklist, returned by Get a Surplus-Lines Filing, the same pair used by Attach Files to a Checklist Item. Resolve them against the checklist of the specific filingId in the request path. A reply is refused with 404 when the checklist item is private, unknown, or has no open escalation, the same response as a filingId your subtree did not file. A resolved escalation cannot be replied to.

Limits

Files attached to a reply follow the same rules as the attachment endpoint:

Allowed types

PDF, DOC, DOCX, JPEG, PNG. Anything else is rejected with 400 before the body is buffered.

10 MB per file

A file larger than that returns 413.
This endpoint supports idempotency. If you include an idempotency-key header, duplicate requests within 1 hour return the original response without reprocessing. See Idempotency.

Error Scenarios

Bad Request (400)

Returned when filingId is not a valid MongoDB ObjectId, a fileโ€™s type is not on the allowed list, or the escalation is already resolved.

Filing or Escalation Not Found (404)

Returned when filingId does not exist, was not filed by your subtree, or the checklist item identified by sourceCategoryId / sourceTaskId is private, unknown, or has no open escalation.

Payload Too Large (413)

Returned when any attached file exceeds 10 MB.

Unauthorized (401)

Missing or invalid authentication token. See Authentication.

Authorizations

Authorization
string
header
required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Headers

idempotency-key
string

UUID to ensure idempotent request processing

Example:

"550e8400-e29b-41d4-a716-446655440000"

x-idempotency-key
string

Alternative UUID header for idempotent request processing

Example:

"550e8400-e29b-41d4-a716-446655440000"

Path Parameters

filingId
string
required

Unique identifier of the surplus-lines filing

Example:

"6650a1b2c3d4e5f6a7b8c9d0"

Body

sourceCategoryId
string
required

sourceCategoryId of the checklist item, from the filing checklist response

Example:

"6650a1b2c3d4e5f6a7b8c9d0"

sourceTaskId
string
required

sourceTaskId of the checklist item, from the filing checklist response

Example:

"6650a1b2c3d4e5f6a7b8c9d1"

body
string

Reply message text; omit when the reply carries only file attachments

Example:

"Signed form attached."

files
file[]

Optional files to attach to the reply. Maximum 10MB per file.

Response

Filing with the escalation reply in place

data
object
required
requestId
string
required

Unique request identifier

Example:

"dev-2c5e7cf2-9acf-4c8c-ab2f-b81f39d775a8"

timestamp
string
required

Response timestamp

Example:

"2025-11-12T20:49:03.293Z"