Skip to main content
POST
Attach uploaded files to a checklist item
Attaches Surplus Lines files you already uploaded to a public checklist item on a filing belonging to the authenticated upstream entity, identified by fileDocumentId. Returns the filing with the new attachments in place. It replaces Attach Files to a Checklist Item, which is deprecated. Send a JSON body: sourceCategoryId and sourceTaskId, plus fileDocumentIds, an array of 1 to 10 distinct ids.

The flow

  1. Upload each file with Upload a Document, using the category Surplus Lines. Each file can be a PDF, DOC, DOCX, JPEG or PNG, up to 10 MB.
  2. Read the _id of each document the uploads return. Those are the fileDocumentIds.
  3. Call this endpoint with the filing’s id, the checklist item’s ids, and the fileDocumentIds.

Identifying the checklist item

sourceCategoryId and sourceTaskId come from the filing’s own checklist, returned by Get a Surplus Lines Filing. That pair identifies an item within one filing only, so always resolve it against the checklist of the specific filingId you are posting to. Checklist content Turris keeps internal is excluded from the checklist response entirely, so there is no id to obtain for it. Posting to a private or unknown item returns 404, the same response as an unrecognized filingId.

Which files are accepted

Every file must be a Surplus Lines upload of your own that is not on any filing yet. If any one of them is not, the whole call returns 404 and nothing is attached. That covers a file already on a filing, a file in another category, a file another organization uploaded, and a file that has been deleted. 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, sourceCategoryId, sourceTaskId or a fileDocumentIds entry is not a valid MongoDB ObjectId, or fileDocumentIds is empty, has duplicates, or has more than 10 entries.

Filing, Checklist Item or File Not Found (404)

Returned when filingId does not exist or belongs to a different upstream entity, the checklist item is private or unknown, or a file is not an unattached Surplus Lines upload of yours.

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"

fileDocumentIds
string[]
required

fileDocumentIds the upload returned for Surplus Lines files that are not yet on any filing. 1 to 10, no duplicates.

Example:

Response

Filing with the new attachments

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"