CLclio
Matter Dockets

Preview calendar dates for the docket

Changed on

Calculates the calendar entries a matter docket would create for the given jurisdiction, trigger and start date, without saving anything. The response is a matter docket containing only calendar_entries, each including summary, description, start_at, end_at and all_day. meta.records is the number of calendar entries. Unknown or mismatched jurisdiction, trigger and service type ids return 422 Unprocessable Entity.

get/court_rules/matter_dockets/preview.json

Request

  • Base URL
    https://app.clio.com/api/v4
  • URL
    https://app.clio.com/api/v4/court_rules/matter_dockets/preview.json
  • Auth
    none declared

Query parameters

event_prefixstring

The prefix that will be added to the beginning of all court rule event titles

jurisdiction[id]integer required

The unique identifier for a single Jurisdiction the account is subscribed to.

service_type[id]integer

The unique identifier for a single service type. Adjusts deadlines for the method of service.

start_datestring date required

The date of the triggering event. (Expects an ISO-8601 date).

start_timestring date-time

The time of the triggering event. (Expects an ISO-8601 timestamp). Some triggers only produce events when a time is supplied.

trigger[id]integer required

The unique identifier for a single Trigger within the Jurisdiction, as returned by the Jurisdictions To Triggers endpoint.

Response

Ok

Changes

  • 20bd96c12901Revision changes
    • breaking

      for the query request parameter start_date, the format changed from date-time to date

    • info

      the query request parameter service_type[id] became optional

    • info

      the query request parameter start_time became optional

    • info

      added the non-success response with the status

    • info

      added the non-success response with the status

    • info

      removed the non-success response with the status

    • info

      removed the non-success response with the status

    • info

      added the success response with the status