Skip to main content
This event fires every time a document is officially added to a case’s docket — whether filed by the claimant, respondent, or case manager. Use it to trigger workflows like logging filings, notifying your team, or automatically preparing a response.

​
Payload

​
entryID
string
required
Unique identifier for this docket entry.
​
enteredAt
string
required
ISO 8601 timestamp of when the entry was added to the docket.
​
filingID
string
required
Unique identifier for the document filing.
​
caseID
string
required
The case this filing belongs to.
​
phaseID
string
required
The phase the case was in when the document was filed. See Schemas for valid phase IDs.
​
documentID
string
required
The type of document that was filed (e.g. statementOfClaim, statementOfResponse, motion). See Schemas for all document types.
​
userID
string
required
The user who filed the document.
​
organizationID
string
The organization of the user who filed, if applicable.
​
partyID
string
required
The party role of the filer (e.g. claimant, respondent, caseManager).
​
rootEntryID
string
If this entry is related to another docket entry, the ID of the root entry in the chain.
​
parentEntryID
string
If this entry is a direct reply to another docket entry, the ID of the parent entry.

​
Example

{
  "id": "9e9d96c0d6dd",
  "timestamp": "2025-08-15T14:32:10Z",
  "event": "docket_filing",
  "data": {
    "entryID": "14",
    "enteredAt": "2025-08-15T14:32:09Z",
    "filingID": "12",
    "caseID": "2025-08-00292",
    "phaseID": "response",
    "documentID": "statementOfResponse",
    "userID": "fa386739-9ff0-4c05-a355-7a21679f2bee",
    "organizationID": "04d9e4f5-4b00-41b1-9164-60c880ffb64e",
    "partyID": "respondent",
    "rootEntryID": null,
    "parentEntryID": null
  }
}