Skip to main content
GET
cURL
Returns a single surplus lines filing by its unique identifier: its checklist, with each item’s ids, files and escalation, the policy document, and any completion artifacts (accepted/stamped filing, receipt, confirmation, tax/remittance proof). Every file comes with short-lived presigned download links. The filing must belong to the authenticated upstream entity. This is where the sourceCategoryId and sourceTaskId come from that Attach Uploaded Files to a Checklist Item and Reply to a Checklist Item Escalation take. See Files on a Surplus Lines Filing.

Path Parameters

Response Shape

All successful responses are wrapped in the standard response envelope. See Request/Response Conventions.

Response Fields

The filing carries the same summary fields as each item in List Surplus Lines Filings, plus the detail fields below.

Checklist category object

Checklist item object

Policy document object

Escalation object

Completion artifact object

downloadUrl and viewUrl are short-lived presigned links. Fetch them fresh from this endpoint when you need a file rather than storing the URL.

Error Scenarios

Bad Request (400)

Returned when filingId is not a valid MongoDB ObjectId format.

Filing Not Found (404)

Returned when filingId doesn’t exist or belongs to a different upstream entity.

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.

Path Parameters

filingId
string
required

Unique identifier of the surplus-lines filing

Example:

"6650a1b2c3d4e5f6a7b8c9d0"

Response

Surplus-lines filing detail with escalations and completion artifacts

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"