Skip to main content
POST
Reply to a checklist item escalation
Send files as fileDocumentIds: upload each one with Upload a Document (category Surplus Lines) first, then pass the returned ids in a JSON body.
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 a JSON body: sourceCategoryId and sourceTaskId, plus an optional body (the message) and an optional fileDocumentIds array of 1 to 10 Surplus Lines files you already uploaded. Send at least a message or one file; a reply with neither returns 400. Files you send land on the checklist item’s attachments, linked to your message.

Identifying the checklist item

sourceCategoryId and sourceTaskId come from the filing’s own checklist, returned by Get a Surplus-Lines Filing: the item Turris is waiting on has escalation.status of waiting customer input. It is the same pair Attach Uploaded Files to a Checklist Item takes. 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 or unknown, the same response as a filingId your subtree did not file. An item with no escalation, or with a resolved escalation, is refused with 400.

Limits

These limits apply when you upload each file with Upload a Document:

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, the reply has neither a message nor a file, the checklist item has no escalation, or the escalation is already resolved. Also returned when fileDocumentIds is empty, has duplicates, has more than 10 entries, or holds values that are not valid ids, and when the request is sent as multipart/form-data instead of a JSON body.

Filing or Escalation Not Found (404)

Returned when filingId does not exist, was not filed by your subtree, the checklist item identified by sourceCategoryId / sourceTaskId is private or unknown, or a fileDocumentIds entry is not an unattached Surplus Lines upload of your subtree.

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

application/json
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."

fileDocumentIds
string[]

Already-uploaded Surplus Lines files to attach to the reply, by the fileDocumentId the upload returned. 1 to 10, no duplicates. Omit for a reply with only a message.

Example:

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"