Lawmatics | Events

Create an event (appointment) in Lawmatics. Provide the name, start/end times, the hosting firm user IDs, the event type, and the ID of exactly one entity (matter or contact — companies cannot have appointments) the appointment is with. Optionally set a description, location, reminder, time zone, and invite behavior.

Cancel an event/appointment in Lawmatics by ID. Cancellation cannot be undone, but the event record is retained: it remains retrievable and listed with its canceledAt timestamp set. Optionally notify the attendees. Canceling an already-canceled event succeeds without change.

Fetch a single event (appointment) from Lawmatics by ID, including its schedule, reminder settings, location, attendee details, cancellation state, and a `relationships` envelope of {id,type} pointers to related records (the matter/contact it is with, event type, address, location, and hosting firm users).

List events (appointments) from Lawmatics with optional pagination, filtering, and sorting. Each row carries the schedule, reminder settings, cancellation state, and a `relationships` envelope of to-one {id,type} pointers (the matter/contact the appointment is with, event type, address, location); use get-event for full details including the hosting firm users. Canceled events are included; check canceledAt. Filter by name, start_date/end_date/canceled_at (datetimes — see the filter.value description), all_day, event_type_id, location_id, or matter_id/prospect_id/contact_id (the eventable association); one filter per request. Date-window recipe — "starts-in-window" semantics: an event belongs to the window if its start_date falls in [window start, window end); an event that began earlier and overlaps the window is NOT included. To resolve a local calendar day/week boundary (not just an absolute instant) into the window start/end values, do that resolution in the intended IANA time zone (DST-safe) before converting to UTC for filter.value — without a known zone, only an absolute-instant window is meaningful. EXHAUSTIVE for a stable dataset (not a point-in-time snapshot — concurrent edits during the walk can shift which page a row lands on): set filter.field 'start_date', operator '>=', value the window start; sortBy 'id', sortOrder 'asc' (the only sort proven complete across page boundaries). Check page 1's pagination.totalPages/totalEntries, walk every page, dedupe rows by id, and cap the walk at a finite page budget. For each returned row, parse startDate AND the window end as instants and compare them — never a lexical string compare, since Lawmatics returns startDate in the firm's own offset while the window end is a UTC instant; discard rows with a null startDate or a non-null canceledAt, and discard rows whose startDate instant is >= the window end instant. BEST-EFFORT ONLY: sortBy 'start_date', sortOrder 'asc' with an early stop once a row's startDate instant reaches the window end is cheaper, but Lawmatics paginates by offset with no secondary sort key, so appointments sharing a start time can be skipped at a page boundary and deduping cannot recover them — do not use it for an exhaustive answer.

Update an existing event (appointment) in Lawmatics by ID. Provide only the fields to change — the API merges, so omitted fields are preserved. Optionally re-attach the appointment to a different matter or contact (companies cannot have appointments).