The Clio connector lets your AI agent act in each user's Clio account. Each user signs in to Clio once, and Scalekit stores and refreshes their tokens, so your agent never handles credentials. It comes with 30 tools.
- Tools
- 30
- What they doRead · write · destructive
- 15 · 11 · 415 read11 write4 destructive
- Users sign in with
- OAuth
- OAuth app
- Your own Clio app
Setup
Install the SDK
Terminal window npm install @scalekit-sdk/node dotenvTerminal window pip install scalekit-sdk-python python-dotenvSet your credentials
Add your Scalekit credentials to your
.envfile. Find values in app.scalekit.com > Developers > API Credentials..env SCALEKIT_ENVIRONMENT_URL=<your-environment-url>SCALEKIT_CLIENT_ID=<your-client-id>SCALEKIT_CLIENT_SECRET=<your-client-secret>Create the Clio connection
In AgentKit > Connections, create a Clio connection and copy its redirect URI. The name you give it is the
connection_nameyour code passes. See Configure connections.Register an OAuth app
Clio connections use your own OAuth app. Register one with Clio and add the redirect URI you copied.
Then enter the app's Client ID and Client Secret on the Clio connection.
Authorize a user and make your first call
quickstart.mts import { ScalekitClient } from '@scalekit-sdk/node'import 'dotenv/config'import { createInterface } from 'node:readline/promises'const scalekit = new ScalekitClient(process.env.SCALEKIT_ENVIRONMENT_URL,process.env.SCALEKIT_CLIENT_ID,process.env.SCALEKIT_CLIENT_SECRET,)const actions = scalekit.actionsconst connector = 'clio'const identifier = 'user_123'// Generate an authorization link for the userconst { link } = await actions.getAuthorizationLink({ connectionName: connector, identifier })console.log('Authorize Clio:', link)const rl = createInterface({ input: process.stdin, output: process.stdout })await rl.question('Press Enter after authorizing...')rl.close()// Make your first callconst result = await actions.executeTool({connector,identifier,toolName: 'clio_activities_list',toolInput: {},})console.log(result)Terminal window npx tsx quickstart.mtsquickstart.py import osfrom scalekit import ScalekitClientfrom dotenv import load_dotenvload_dotenv()scalekit_client = ScalekitClient(env_url=os.getenv("SCALEKIT_ENVIRONMENT_URL"),client_id=os.getenv("SCALEKIT_CLIENT_ID"),client_secret=os.getenv("SCALEKIT_CLIENT_SECRET"),)actions = scalekit_client.actionsconnection_name = "clio"identifier = "user_123"# Generate an authorization link for the userlink_response = actions.get_authorization_link(connection_name=connection_name,identifier=identifier,)print("Authorize Clio:", link_response.link)input("Press Enter after authorizing...")# Make your first callresult = actions.execute_tool(tool_input={},tool_name="clio_activities_list",connection_name=connection_name,identifier=identifier,)print(result)Terminal window python quickstart.pyEach user signs in once. See Authorize a user for the full flow and statuses.
Tools
Pass the exact name toexecute_toolclio_activities_listList time and expense entries, filtered by matter, user, type, status, date range or a search on the note.Read-onlyList Activities
List time and expense entries, filtered by matter, user, type, status, date range or a search on the note. Returns data[] of activities (type, date, hours, price, total, note, billed state, matter, user) and meta.paging. Use clio_activities_list to review billable work. Use clio_activity_create to log time or an expense.
Inputs
end_datestring- Entries dated on or before this date (YYYY-MM-DD). Example: 2026-11-30
fieldsstring- Comma-separated fields to return; nested records use braces. Clio returns only id and etag when fields is empty, so a useful default is set. Example: id,etag,type,date,quantity_in_hours,price,total,note,billed,non_billable,matter{id,display_number},user{id,name},activity_description{id,name},created_at,updated_atdefault
id,etag,type,date,quantity_in_hours,price,total,note,billed,non_billable,matter{id,display_number},user{id,name},activity_description{id,name},created_at,updated_at limitinteger- Records per page, 1-200 (default 200). Example: 50
matter_idinteger- Only entries on this matter. Example: 1234567
orderstring- Sort order, such as date(desc), id(asc) or total(desc). Example: date(desc)
page_tokenstring- Token for the next page, taken from meta.paging.next in the previous response. Example: BAh7BjoLb2Zmc2V0aQH6
querystring- Wildcard search over the entry note. Example: research
start_datestring- Entries dated on or after this date (YYYY-MM-DD). Example: 2026-11-01
statusstring- billed, draft, unbilled, non_billable, billable or written_off. Example: unbilledone of
billeddraftunbillednon_billablebillablewritten_off typestring- TimeEntry, ExpenseEntry, HardCostEntry, SoftCostEntry or FixedFee. Example: TimeEntryone of
TimeEntryExpenseEntryHardCostEntrySoftCostEntryFixedFee user_idinteger- Only entries by this user. Example: 345678
clio_bill_getGet one bill.Read-onlyGet Bill
Get one bill. Returns data with the requested bill fields. Use clio_bill_get when you know the bill ID. Use clio_bills_list to search.
Inputs
bill_idintegerrequired- ID of the bill. Example: 1234567
fieldsstring- Comma-separated fields to return; nested records use braces. Clio returns only id and etag when fields is empty, so a useful default is set. Example: id,etag,number,state,kind,issued_at,due_at,total,paid,balance,due,subject,client{id,name},matters{id,display_number},created_at,updated_atdefault
id,etag,number,state,kind,issued_at,due_at,total,paid,balance,due,subject,client{id,name},matters{id,display_number},created_at,updated_at
clio_bills_listList bills (invoices), filtered by client, matter, state, overdue status or issue and due dates.Read-onlyList Bills
List bills (invoices), filtered by client, matter, state, overdue status or issue and due dates. Returns data[] of bills (number, state, issued and due dates, total, paid, balance, client, matters) and meta.paging. Use clio_bills_list to check invoices and balances. Use clio_bill_get for one bill.
Inputs
client_idinteger- Only bills for this client contact. Example: 1234568
due_beforestring- Due before this date (YYYY-MM-DD). Example: 2026-12-01
fieldsstring- Comma-separated fields to return; nested records use braces. Clio returns only id and etag when fields is empty, so a useful default is set. Example: id,etag,number,state,kind,issued_at,due_at,total,paid,balance,due,subject,client{id,name},matters{id,display_number},created_at,updated_atdefault
id,etag,number,state,kind,issued_at,due_at,total,paid,balance,due,subject,client{id,name},matters{id,display_number},created_at,updated_at issued_afterstring- Issued after this date (YYYY-MM-DD). Example: 2026-10-01
limitinteger- Records per page, 1-200 (default 200). Example: 50
matter_idinteger- Only bills for this matter. Example: 1234567
overdue_onlyboolean- Only overdue bills. Example: true
page_tokenstring- Token for the next page, taken from meta.paging.next in the previous response. Example: BAh7BjoLb2Zmc2V0aQH6
statestring- draft, awaiting_approval, awaiting_payment, paid, void or deleted. Example: awaiting_paymentone of
draftawaiting_approvalawaiting_paymentpaidvoiddeleted
clio_calendar_entries_listList calendar entries in a time range, optionally for one calendar or matter, with recurring events expanded.Read-onlyList Calendar Entries
List calendar entries in a time range, optionally for one calendar or matter, with recurring events expanded. Returns data[] of entries (summary, start_at, end_at, all_day, location, matter, calendar owner) and meta.paging. Use clio_calendar_entries_list to check a schedule. Use clio_calendar_entry_create to add an event.
Inputs
calendar_idinteger- Only entries on this calendar. Example: 456789
expandedboolean- Return each occurrence of recurring events. Example: true
fieldsstring- Comma-separated fields to return; nested records use braces. Clio returns only id and etag when fields is empty, so a useful default is set. Example: id,etag,summary,description,location,start_at,end_at,all_day,recurrence_rule,matter{id,display_number},calendar_owner{id,name},created_at,updated_atdefault
id,etag,summary,description,location,start_at,end_at,all_day,recurrence_rule,matter{id,display_number},calendar_owner{id,name},created_at,updated_at fromstring- Entries ending on or after this ISO-8601 time. Example: 2026-11-15T00:00:00Z
limitinteger- Records per page, 1-200 (default 200). Example: 50
matter_idinteger- Only entries for this matter. Example: 1234567
page_tokenstring- Token for the next page, taken from meta.paging.next in the previous response. Example: BAh7BjoLb2Zmc2V0aQH6
querystring- Wildcard search over calendar entries. Example: hearing
tostring- Entries starting on or before this ISO-8601 time. Example: 2026-11-22T23:59:59Z
clio_calendars_listList calendars the connected user can see.Read-onlyList Calendars
List calendars the connected user can see. Returns data[] of calendars with id, name, type (UserCalendar, AccountCalendar, AdhocCalendar), permission and visibility. Use clio_calendars_list to get the calendar ID needed by clio_calendar_entry_create.
Inputs
fieldsstring- Comma-separated fields to return; nested records use braces. Clio returns only id and etag when fields is empty, so a useful default is set. Example: id,etag,name,type,permission,visible,colordefault
id,etag,name,type,permission,visible,color limitinteger- Records per page, 1-200 (default 200). Example: 50
ownerboolean- Only calendars the user owns. Example: true
page_tokenstring- Token for the next page, taken from meta.paging.next in the previous response. Example: BAh7BjoLb2Zmc2V0aQH6
typestring- AccountCalendar, AdhocCalendar or UserCalendar. Example: UserCalendarone of
AccountCalendarAdhocCalendarUserCalendar writeableboolean- Only calendars the user can write to. Example: true
clio_communications_listList logged emails and phone calls, filtered by matter, contact, user, type, date range or a search string.Read-onlyList Communications
List logged emails and phone calls, filtered by matter, contact, user, type, date range or a search string. Returns data[] of communications (type, subject, body, received_at, matter, senders, receivers) and meta.paging. Use clio_communications_list to review client correspondence. Use clio_communication_create to log a call or email.
Inputs
contact_idinteger- Only communications with this contact. Example: 1234568
fieldsstring- Comma-separated fields to return; nested records use braces. Clio returns only id and etag when fields is empty, so a useful default is set. Example: id,etag,type,subject,body,date,received_at,matter{id,display_number},user{id,name},senders{id,name,type},receivers{id,name,type},created_at,updated_atdefault
id,etag,type,subject,body,date,received_at,matter{id,display_number},user{id,name},senders{id,name,type},receivers{id,name,type},created_at,updated_at limitinteger- Records per page, 1-200 (default 200). Example: 50
matter_idinteger- Only communications on this matter. Example: 1234567
page_tokenstring- Token for the next page, taken from meta.paging.next in the previous response. Example: BAh7BjoLb2Zmc2V0aQH6
querystring- Wildcard search over communication body and subject. Example: settlement
received_beforestring- On or before this date (ISO-8601). Example: 2026-11-30
received_sincestring- On or after this date (ISO-8601). Example: 2026-11-01
typestring- EmailCommunication or PhoneCommunication. Example: PhoneCommunicationone of
EmailCommunicationPhoneCommunication
clio_contact_getGet one contact.Read-onlyGet Contact
Get one contact. Returns data with the requested contact fields. Use clio_contact_get when you know the contact ID. Use clio_contacts_list to search.
Inputs
contact_idintegerrequired- ID of the contact. Example: 1234567
fieldsstring- Comma-separated fields to return; nested records use braces. Clio returns only id and etag when fields is empty, so a useful default is set. Example: id,etag,name,first_name,last_name,type,title,primary_email_address,primary_phone_number,is_client,company{id,name},created_at,updated_atdefault
id,etag,name,first_name,last_name,type,title,primary_email_address,primary_phone_number,is_client,company{id,name},created_at,updated_at
clio_contacts_listList people and companies in Clio, filtered by a search string, type, client flag or update time.Read-onlyList Contacts
List people and companies in Clio, filtered by a search string, type, client flag or update time. Returns data[] of contacts (name, type, primary email and phone, is_client, company) and meta.paging. Use clio_contacts_list to find a contact or client. Use clio_contact_get for one contact by ID.
Inputs
client_onlyboolean- Only contacts that are clients. Example: true
fieldsstring- Comma-separated fields to return; nested records use braces. Clio returns only id and etag when fields is empty, so a useful default is set. Example: id,etag,name,first_name,last_name,type,title,primary_email_address,primary_phone_number,is_client,company{id,name},created_at,updated_atdefault
id,etag,name,first_name,last_name,type,title,primary_email_address,primary_phone_number,is_client,company{id,name},created_at,updated_at limitinteger- Records per page, 1-200 (default 200). Example: 50
orderstring- id(asc), id(desc), name(asc) or name(desc). Example: name(asc)one of
id(asc)id(desc)name(asc)name(desc)shared_at(asc)shared_at(desc) page_tokenstring- Token for the next page, taken from meta.paging.next in the previous response. Example: BAh7BjoLb2Zmc2V0aQH6
querystring- Wildcard search over name, title, email, address, phone, web site, custom fields and related matter. Example: Smith
typestring- Person or Company. Example: Personone of
PersonCompany updated_sincestring- Only records updated after this ISO-8601 time. Example: 2026-11-01T00:00:00Z
clio_matter_getGet one matter.Read-onlyGet Matter
Get one matter. Returns data with the requested matter fields. Use clio_matter_get when you know the matter ID. Use clio_matters_list to search.
Inputs
matter_idintegerrequired- ID of the matter. Example: 1234567
fieldsstring- Comma-separated fields to return; nested records use braces. Clio returns only id and etag when fields is empty, so a useful default is set. Example: id,etag,display_number,description,status,open_date,close_date,pending_date,billable,client_reference,location,client{id,name},responsible_attorney{id,name},originating_attorney{id,name},practice_area{id,name},created_at,updated_atdefault
id,etag,display_number,description,status,open_date,close_date,pending_date,billable,client_reference,location,client{id,name},responsible_attorney{id,name},originating_attorney{id,name},practice_area{id,name},created_at,updated_at
clio_matters_listList matters, filtered by status, client, responsible attorney, practice area, update time or a search string.Read-onlyList Matters
List matters, filtered by status, client, responsible attorney, practice area, update time or a search string. Returns data[] of matters (display_number, description, status, dates, client, attorneys, practice area) and meta.paging. Use clio_matters_list to find matters. Use clio_matter_get for one matter by ID.
Inputs
billableboolean- Only billable (true) or non-billable (false) matters. Example: true
client_idinteger- Only matters for this client contact. Example: 1234567
fieldsstring- Comma-separated fields to return; nested records use braces. Clio returns only id and etag when fields is empty, so a useful default is set. Example: id,etag,display_number,description,status,open_date,close_date,pending_date,billable,client_reference,location,client{id,name},responsible_attorney{id,name},originating_attorney{id,name},practice_area{id,name},created_at,updated_atdefault
id,etag,display_number,description,status,open_date,close_date,pending_date,billable,client_reference,location,client{id,name},responsible_attorney{id,name},originating_attorney{id,name},practice_area{id,name},created_at,updated_at limitinteger- Records per page, 1-200 (default 200). Example: 50
orderstring- Sort order, such as display_number(asc), id(desc), open_date(desc) or updated_at(desc). Example: updated_at(desc)
page_tokenstring- Token for the next page, taken from meta.paging.next in the previous response. Example: BAh7BjoLb2Zmc2V0aQH6
practice_area_idinteger- Only matters in this practice area. Example: 98765
querystring- Wildcard search over display number, number, description and client name. Example: Smith
responsible_attorney_idinteger- Only matters with this responsible attorney (user ID). Example: 345678
statusstring- Comma-separated statuses: open, pending, closed. Example: open,pending
updated_sincestring- Only records updated after this ISO-8601 time. Example: 2026-11-01T00:00:00Z
clio_notes_listList notes on matters or on contacts, filtered by matter, contact or a search string.Read-onlyList Notes
List notes on matters or on contacts, filtered by matter, contact or a search string. Returns data[] of notes (subject, detail, date, matter or contact, author) and meta.paging. Use clio_notes_list to read case notes. Use clio_note_create to add one.
Inputs
typestringrequired- Matter for matter notes, Contact for contact notes. Example: Matterone of
MatterContact contact_idinteger- Only notes on this contact. Example: 1234568
fieldsstring- Comma-separated fields to return; nested records use braces. Clio returns only id and etag when fields is empty, so a useful default is set. Example: id,etag,type,subject,detail,date,matter{id,display_number},contact{id,name},author{id,name},created_at,updated_atdefault
id,etag,type,subject,detail,date,matter{id,display_number},contact{id,name},author{id,name},created_at,updated_at limitinteger- Records per page, 1-200 (default 200). Example: 50
matter_idinteger- Only notes on this matter. Example: 1234567
page_tokenstring- Token for the next page, taken from meta.paging.next in the previous response. Example: BAh7BjoLb2Zmc2V0aQH6
querystring- Wildcard search over note subject and detail. Example: settlement
clio_task_getGet one task.Read-onlyGet Task
Get one task. Returns data with the requested task fields. Use clio_task_get when you know the task ID. Use clio_tasks_list to search.
Inputs
task_idintegerrequired- ID of the task. Example: 1234567
fieldsstring- Comma-separated fields to return; nested records use braces. Clio returns only id and etag when fields is empty, so a useful default is set. Example: id,etag,name,description,status,priority,due_at,completed_at,permission,matter{id,display_number},assignee{id,name,type},created_at,updated_atdefault
id,etag,name,description,status,priority,due_at,completed_at,permission,matter{id,display_number},assignee{id,name,type},created_at,updated_at
clio_tasks_listList tasks, filtered by matter, assignee, status, priority, completion, due-date range or a search string.Read-onlyList Tasks
List tasks, filtered by matter, assignee, status, priority, completion, due-date range or a search string. Returns data[] of tasks (name, description, status, priority, due date, matter, assignee) and meta.paging. Use clio_tasks_list to see open work. Use clio_task_get for one task.
Inputs
assignee_idinteger- Only tasks assigned to this user or contact; set assignee_type too. Example: 345678
assignee_typestring- user or contact; required with assignee_id. Example: userone of
usercontact completeboolean- true for completed tasks, false for open ones. Example: false
due_at_fromstring- Due on or after this date (YYYY-MM-DD). Example: 2026-11-15
due_at_tostring- Due on or before this date (YYYY-MM-DD). Example: 2026-11-30
fieldsstring- Comma-separated fields to return; nested records use braces. Clio returns only id and etag when fields is empty, so a useful default is set. Example: id,etag,name,description,status,priority,due_at,completed_at,permission,matter{id,display_number},assignee{id,name,type},created_at,updated_atdefault
id,etag,name,description,status,priority,due_at,completed_at,permission,matter{id,display_number},assignee{id,name,type},created_at,updated_at limitinteger- Records per page, 1-200 (default 200). Example: 50
matter_idinteger- Only tasks on this matter. Example: 1234567
page_tokenstring- Token for the next page, taken from meta.paging.next in the previous response. Example: BAh7BjoLb2Zmc2V0aQH6
prioritystring- high, normal or low. Example: highone of
highnormallow querystring- Wildcard search over task name and description. Example: discovery
statusstring- pending, in_progress, in_review, complete or draft. Example: pendingone of
pendingin_progressin_reviewcompletedraft
clio_users_listList users in the Clio firm, filtered by name, role, subscription type or enabled state.Read-onlyList Users
List users in the Clio firm, filtered by name, role, subscription type or enabled state. Returns data[] of users with the requested fields and meta.paging for the next page. Use clio_users_list to find a user ID for matters, tasks or time entries. Use clio_who_am_i_get for the connected user.
Inputs
enabledboolean- true for enabled users, false for disabled. Example: true
fieldsstring- Comma-separated fields to return; nested records use braces. Clio returns only id and etag when fields is empty, so a useful default is set. Example: id,etag,name,first_name,last_name,email,enabled,roles,subscription_type,time_zone,default_calendar_iddefault
id,etag,name,first_name,last_name,email,enabled,roles,subscription_type,time_zone,default_calendar_id limitinteger- Records per page, 1-200 (default 200). Example: 50
namestring- Only users with this name. Example: Jane Doe
page_tokenstring- Token for the next page, taken from meta.paging.next in the previous response. Example: BAh7BjoLb2Zmc2V0aQH6
rolestring- Only users with this role: admin, accounts, billing or reports. Example: billingone of
adminaccountsbillingreports subscription_typestring- attorney or nonattorney. Example: attorneyone of
attorneynonattorney
clio_who_am_i_getGet the Clio user the connection belongs to.Read-onlyGet Current User
Get the Clio user the connection belongs to. Returns data with the user's id, name, email, roles, subscription type, time zone and default calendar ID. Use clio_who_am_i_get to learn the connected user's ID and default calendar. Use clio_users_list for other firm users.
Inputs
fieldsstring- Comma-separated fields to return; nested records use braces. Clio returns only id and etag when fields is empty, so a useful default is set. Example: id,etag,name,first_name,last_name,email,enabled,roles,subscription_type,time_zone,default_calendar_iddefault
id,etag,name,first_name,last_name,email,enabled,roles,subscription_type,time_zone,default_calendar_id
clio_activity_createLog a time entry or an expense, usually against a matter.WriteCreate Activity
Log a time entry or an expense, usually against a matter. Returns data with the new activity's id, total and the requested fields. Use clio_activity_create to record billable time or costs. Use clio_activities_list to review entries.
Inputs
datestringrequired- Date the work was done (YYYY-MM-DD). Example: 2026-11-15
typestringrequired- TimeEntry, ExpenseEntry, HardCostEntry, SoftCostEntry or FixedFee. Example: TimeEntryone of
TimeEntryExpenseEntryHardCostEntrySoftCostEntryFixedFee activity_description_idinteger- Activity description (rate category) ID. Example: 22334
fieldsstring- Comma-separated fields to return; nested records use braces. Clio returns only id and etag when fields is empty, so a useful default is set. Example: id,etag,type,date,quantity_in_hours,price,total,note,billed,non_billable,matter{id,display_number},user{id,name},activity_description{id,name},created_at,updated_atdefault
id,etag,type,date,quantity_in_hours,price,total,note,billed,non_billable,matter{id,display_number},user{id,name},activity_description{id,name},created_at,updated_at matter_idinteger- Matter to log against. Example: 1234567
non_billableboolean- Keep the entry off bills. Example: false
notestring- What the entry is for. Example: Drafted motion to dismiss
pricenumber- Hourly rate for a TimeEntry, or the amount for an expense. Example: 250
quantitynumber- For TimeEntry, the time in seconds (4.0.4 and later); for ExpenseEntry and SoftCostEntry, the quantity. Example: 3600
user_idinteger- User who did the work; defaults to the connected user. Example: 345678
clio_activity_updateUpdate an unbilled time or expense entry: date, quantity, rate, note, matter or billable flag.WriteUpdate Activity
Update an unbilled time or expense entry: date, quantity, rate, note, matter or billable flag. Returns data with the updated activity fields. Use clio_activity_update to correct an entry before it is billed.
- Idempotent
Inputs
activity_idintegerrequired- ID of the activity. Example: 1234567
activity_description_idinteger- Activity description (rate category) ID. Example: 22334
datestring- New date (YYYY-MM-DD). Example: 2026-11-14
fieldsstring- Comma-separated fields to return; nested records use braces. Clio returns only id and etag when fields is empty, so a useful default is set. Example: id,etag,type,date,quantity_in_hours,price,total,note,billed,non_billable,matter{id,display_number},user{id,name},activity_description{id,name},created_at,updated_atdefault
id,etag,type,date,quantity_in_hours,price,total,note,billed,non_billable,matter{id,display_number},user{id,name},activity_description{id,name},created_at,updated_at matter_idinteger- Matter to log against. Example: 1234567
non_billableboolean- Keep the entry off bills. Example: false
notestring- What the entry is for. Example: Drafted motion to dismiss
pricenumber- Hourly rate for a TimeEntry, or the amount for an expense. Example: 250
quantitynumber- For TimeEntry, the time in seconds (4.0.4 and later); for ExpenseEntry and SoftCostEntry, the quantity. Example: 3600
user_idinteger- User who did the work; defaults to the connected user. Example: 345678
clio_calendar_entry_createCreate an event on a Clio calendar, optionally linked to a matter.WriteCreate Calendar Entry
Create an event on a Clio calendar, optionally linked to a matter. Returns data with the new entry's id and the requested fields. Use clio_calendar_entry_create to schedule a hearing or meeting. Get calendar_id from clio_calendars_list or clio_who_am_i_get (default_calendar_id).
Inputs
calendar_idintegerrequired- Calendar to put the entry on. Example: 456789
end_atstringrequired- End time (ISO-8601). Example: 2026-11-20T16:00:00Z
start_atstringrequired- Start time (ISO-8601). Example: 2026-11-20T15:00:00Z
summarystringrequired- Short title. Example: Hearing - Smith v. Jones
all_dayboolean- All-day event. Example: false
descriptionstring- Details. Example: Courtroom 4B
fieldsstring- Comma-separated fields to return; nested records use braces. Clio returns only id and etag when fields is empty, so a useful default is set. Example: id,etag,summary,description,location,start_at,end_at,all_day,recurrence_rule,matter{id,display_number},calendar_owner{id,name},created_at,updated_atdefault
id,etag,summary,description,location,start_at,end_at,all_day,recurrence_rule,matter{id,display_number},calendar_owner{id,name},created_at,updated_at locationstring- Location. Example: 361 University Ave, Toronto
matter_idinteger- Matter to link. Example: 1234567
recurrence_rulestring- iCalendar RRULE for a repeating event. Example: FREQ=WEEKLY;COUNT=4
clio_communication_createLog a phone call or email in Clio, optionally on a matter with senders and receivers; nothing is sent.WriteLog Communication
Log a phone call or email in Clio, optionally on a matter with senders and receivers; nothing is sent. Returns data with the new communication's id and the requested fields. Use clio_communication_create to record correspondence on a matter.
Inputs
bodystringrequired- What was said or written. Example: Client confirmed documents will be sent Friday
received_atstringrequired- When it happened (ISO-8601 date-time). Example: 2026-11-15T14:30:00Z
subjectstringrequired- Subject. Example: Call with client re discovery
typestringrequired- PhoneCommunication or EmailCommunication. Example: PhoneCommunicationone of
PhoneCommunicationEmailCommunication fieldsstring- Comma-separated fields to return; nested records use braces. Clio returns only id and etag when fields is empty, so a useful default is set. Example: id,etag,type,subject,body,date,received_at,matter{id,display_number},user{id,name},senders{id,name,type},receivers{id,name,type},created_at,updated_atdefault
id,etag,type,subject,body,date,received_at,matter{id,display_number},user{id,name},senders{id,name,type},receivers{id,name,type},created_at,updated_at matter_idinteger- Matter to log it on. Example: 1234567
receiversarray- Receivers, each {"id": ..., "type": "User" or "Contact"}. Example: [{"id": 345678, "type": "User"}]
sendersarray- Senders, each {"id": ..., "type": "User" or "Contact"}. Example: [{"id": 1234568, "type": "Contact"}]
clio_contact_createCreate a person or company contact.WriteCreate Contact
Create a person or company contact. Returns data with the new contact's id and the requested fields. Use clio_contact_create to add a client or other party. Use clio_contacts_list first to avoid duplicates.
Inputs
namestringrequired- Full name of the person, or the company name. Example: Jane Smith
typestringrequired- Person or Company. Example: Personone of
PersonCompany addressesarray- Addresses, each {name: Work, Home, Billing or Other, street, city, province, postal_code, country}. Example: [{"name": "Work", "street": "1 King St W", "city": "Toronto", "province": "ON", "postal_code": "M5H 1A1", "country": "Canada"}]
company_idinteger- Contact ID of the company this person works for. Example: 1234568
email_addressesarray- Email addresses, each {name: Work, Home or Other, address, default_email}. Example: [{"name": "Work", "address": "jane@example.com", "default_email": true}]
fieldsstring- Comma-separated fields to return; nested records use braces. Clio returns only id and etag when fields is empty, so a useful default is set. Example: id,etag,name,first_name,last_name,type,title,primary_email_address,primary_phone_number,is_client,company{id,name},created_at,updated_atdefault
id,etag,name,first_name,last_name,type,title,primary_email_address,primary_phone_number,is_client,company{id,name},created_at,updated_at first_namestring- First name (Person). Example: Jane
last_namestring- Last name (Person). Example: Smith
phone_numbersarray- Phone numbers, each {name: Work, Home, Mobile, Fax, Pager, Skype or Other, number, default_number}. Example: [{"name": "Work", "number": "555-0100", "default_number": true}]
titlestring- Professional title. Example: General Counsel
clio_contact_updateUpdate a contact's name, title, emails, phone numbers, addresses or company.WriteUpdate Contact
Update a contact's name, title, emails, phone numbers, addresses or company. Returns data with the updated contact fields. Use clio_contact_update to change contact details. Email, phone and address arrays add entries; include an id to change an existing one.
- Idempotent
Inputs
contact_idintegerrequired- ID of the contact. Example: 1234567
addressesarray- Addresses, each {name: Work, Home, Billing or Other, street, city, province, postal_code, country}. Example: [{"name": "Work", "street": "1 King St W", "city": "Toronto", "province": "ON", "postal_code": "M5H 1A1", "country": "Canada"}]
company_idinteger- Contact ID of the company this person works for. Example: 1234568
email_addressesarray- Email addresses, each {name: Work, Home or Other, address, default_email}. Example: [{"name": "Work", "address": "jane@example.com", "default_email": true}]
fieldsstring- Comma-separated fields to return; nested records use braces. Clio returns only id and etag when fields is empty, so a useful default is set. Example: id,etag,name,first_name,last_name,type,title,primary_email_address,primary_phone_number,is_client,company{id,name},created_at,updated_atdefault
id,etag,name,first_name,last_name,type,title,primary_email_address,primary_phone_number,is_client,company{id,name},created_at,updated_at first_namestring- First name (Person). Example: Jane
last_namestring- Last name (Person). Example: Smith
namestring- New full name or company name. Example: Jane A. Smith
phone_numbersarray- Phone numbers, each {name: Work, Home, Mobile, Fax, Pager, Skype or Other, number, default_number}. Example: [{"name": "Work", "number": "555-0100", "default_number": true}]
titlestring- Professional title. Example: General Counsel
clio_matter_createCreate a matter for a client contact.WriteCreate Matter
Create a matter for a client contact. Returns data with the new matter's id, display_number and the requested fields. Use clio_matter_create to open a new case. Create or find the client with clio_contact_create or clio_contacts_list first.
Inputs
client_idintegerrequired- Contact ID of the client. Example: 1234567
descriptionstringrequired- Description of the matter. Example: Smith v. Jones - contract dispute
billableboolean- Whether the matter is billable. Example: true
client_referencestring- Client reference for your own use. Example: PO-4471
close_datestring- Close date (YYYY-MM-DD). Example: 2026-12-31
fieldsstring- Comma-separated fields to return; nested records use braces. Clio returns only id and etag when fields is empty, so a useful default is set. Example: id,etag,display_number,description,status,open_date,close_date,pending_date,billable,client_reference,location,client{id,name},responsible_attorney{id,name},originating_attorney{id,name},practice_area{id,name},created_at,updated_atdefault
id,etag,display_number,description,status,open_date,close_date,pending_date,billable,client_reference,location,client{id,name},responsible_attorney{id,name},originating_attorney{id,name},practice_area{id,name},created_at,updated_at locationstring- Location of the matter. Example: Toronto
open_datestring- Open date (YYYY-MM-DD). Example: 2026-11-15
originating_attorney_idinteger- User ID of the originating attorney. Example: 345678
practice_area_idinteger- Practice area ID. Example: 98765
responsible_attorney_idinteger- User ID of the responsible attorney. Example: 345678
statusstring- open, pending or closed. Example: openone of
openpendingclosed
clio_matter_updateUpdate a matter's description, status, dates, attorneys, practice area or billing flag.WriteUpdate Matter
Update a matter's description, status, dates, attorneys, practice area or billing flag. Returns data with the updated matter fields. Use clio_matter_update to change or close a matter. Use clio_matter_get first to see current values.
- Idempotent
Inputs
matter_idintegerrequired- ID of the matter. Example: 1234567
billableboolean- Whether the matter is billable. Example: true
client_referencestring- Client reference for your own use. Example: PO-4471
close_datestring- Close date (YYYY-MM-DD). Example: 2026-12-31
descriptionstring- New description. Example: Smith v. Jones - settled
fieldsstring- Comma-separated fields to return; nested records use braces. Clio returns only id and etag when fields is empty, so a useful default is set. Example: id,etag,display_number,description,status,open_date,close_date,pending_date,billable,client_reference,location,client{id,name},responsible_attorney{id,name},originating_attorney{id,name},practice_area{id,name},created_at,updated_atdefault
id,etag,display_number,description,status,open_date,close_date,pending_date,billable,client_reference,location,client{id,name},responsible_attorney{id,name},originating_attorney{id,name},practice_area{id,name},created_at,updated_at locationstring- Location of the matter. Example: Toronto
open_datestring- Open date (YYYY-MM-DD). Example: 2026-11-15
originating_attorney_idinteger- User ID of the originating attorney. Example: 345678
practice_area_idinteger- Practice area ID. Example: 98765
responsible_attorney_idinteger- User ID of the responsible attorney. Example: 345678
statusstring- open, pending or closed. Example: openone of
openpendingclosed
clio_note_createAdd a note to a matter or a contact.WriteCreate Note
Add a note to a matter or a contact. Returns data with the new note's id and the requested fields. Use clio_note_create to record case information. Set type Matter with matter_id, or type Contact with contact_id.
Inputs
typestringrequired- Matter or Contact. Example: Matterone of
MatterContact contact_idinteger- Contact the note belongs to; required when type is Contact. Example: 1234568
datestring- Note date (YYYY-MM-DD). Example: 2026-11-15
detailstring- Note text. Example: Opposing counsel open to mediation in December
fieldsstring- Comma-separated fields to return; nested records use braces. Clio returns only id and etag when fields is empty, so a useful default is set. Example: id,etag,type,subject,detail,date,matter{id,display_number},contact{id,name},author{id,name},created_at,updated_atdefault
id,etag,type,subject,detail,date,matter{id,display_number},contact{id,name},author{id,name},created_at,updated_at matter_idinteger- Matter the note belongs to; required when type is Matter. Example: 1234567
subjectstring- Note subject. Example: Settlement call
clio_task_createCreate a task, optionally on a matter and assigned to a user or contact.WriteCreate Task
Create a task, optionally on a matter and assigned to a user or contact. Returns data with the new task's id and the requested fields. Use clio_task_create to add a to-do. Use clio_task_update to complete or change it.
Inputs
descriptionstringrequired- Task description. Example: File with the court by end of day
namestringrequired- Task name. Example: File statement of claim
assigneeobject- Who the task is for, as {"id": ..., "type": "User" or "Contact"}. Example: {"id": 345678, "type": "User"}
due_atstring- Due date (YYYY-MM-DD). Example: 2026-11-30
fieldsstring- Comma-separated fields to return; nested records use braces. Clio returns only id and etag when fields is empty, so a useful default is set. Example: id,etag,name,description,status,priority,due_at,completed_at,permission,matter{id,display_number},assignee{id,name,type},created_at,updated_atdefault
id,etag,name,description,status,priority,due_at,completed_at,permission,matter{id,display_number},assignee{id,name,type},created_at,updated_at matter_idinteger- Matter the task belongs to. Example: 1234567
notify_assigneeboolean- Email the assignee about the task. Example: false
prioritystring- High, Normal or Low. Example: Highone of
HighNormalLow statusstring- pending, in_progress, in_review, complete or draft (without advanced tasks only pending or complete). Example: completeone of
pendingin_progressin_reviewcompletedraft
clio_task_updateUpdate a task: rename it, change due date, priority, status, matter or assignee, or mark it complete.WriteUpdate Task
Update a task: rename it, change due date, priority, status, matter or assignee, or mark it complete. Returns data with the updated task fields. Use clio_task_update with status complete to finish a task.
- Idempotent
Inputs
task_idintegerrequired- ID of the task. Example: 1234567
assigneeobject- Who the task is for, as {"id": ..., "type": "User" or "Contact"}. Example: {"id": 345678, "type": "User"}
descriptionstring- New description. Example: Filed on 15 Nov
due_atstring- Due date (YYYY-MM-DD). Example: 2026-11-30
fieldsstring- Comma-separated fields to return; nested records use braces. Clio returns only id and etag when fields is empty, so a useful default is set. Example: id,etag,name,description,status,priority,due_at,completed_at,permission,matter{id,display_number},assignee{id,name,type},created_at,updated_atdefault
id,etag,name,description,status,priority,due_at,completed_at,permission,matter{id,display_number},assignee{id,name,type},created_at,updated_at matter_idinteger- Matter the task belongs to. Example: 1234567
namestring- New name. Example: File amended claim
notify_assigneeboolean- Email the assignee about the task. Example: false
prioritystring- High, Normal or Low. Example: Highone of
HighNormalLow statusstring- pending, in_progress, in_review, complete or draft (without advanced tasks only pending or complete). Example: completeone of
pendingin_progressin_reviewcompletedraft
clio_activity_deleteDelete an unbilled time or expense entry.DestructiveDelete Activity
Delete an unbilled time or expense entry. Returns no content (HTTP 204) when deleted. Use clio_activity_delete to remove an entry logged by mistake; billed entries can't be deleted.
- Idempotent
Inputs
activity_idintegerrequired- ID of the activity. Example: 1234567
clio_calendar_entry_deleteDelete a calendar entry.DestructiveDelete Calendar Entry
Delete a calendar entry. Returns no content (HTTP 204) when deleted. Use clio_calendar_entry_delete with an ID from clio_calendar_entries_list.
- Idempotent
Inputs
calendar_entry_idintegerrequired- ID of the calendar entry. Example: 1234567
clio_contact_deleteDelete a contact.DestructiveDelete Contact
Delete a contact. Returns no content (HTTP 204) when deleted. Use clio_contact_delete only to remove a contact for good; clients with matters can't be deleted.
- Idempotent
Inputs
contact_idintegerrequired- ID of the contact. Example: 1234567
clio_task_deleteDelete a task.DestructiveDelete Task
Delete a task. Returns no content (HTTP 204) when deleted. Use clio_task_delete to remove a task; use clio_task_update with status complete to finish one instead.
- Idempotent
Inputs
task_idintegerrequired- ID of the task. Example: 1234567
No tools match.