API documentation for LegalOn services
- Delete a matter
LegalOn API (1.2.0)
Request
Partially updates matter fields, the requester, requesting department, status, assignees, and custom attributes in one request.
- When a requester is specified, LegalOn resolves an active user first; if no matching user exists, it reuses an existing guest or creates a new guest.
- If requester is omitted, the existing requester is retained; other omitted fields remain unchanged.
Matter partial update request.
Matter due date. Set to null to clear the due date; omit to leave it unchanged.
Requester identified by email address and name. A user or guest ID cannot be specified directly.
Complete list of sub-assignee user IDs. An empty array clears all sub-assignees. The same user ID cannot be specified more than once.
- The server URL is `{api_base_url}/rest/v1`.
You can construct the server URL using the value of `api_base_url` provided in the response when obtaining an access token.
https://{api_base_url_without_scheme}/rest/v1/matters/{matter_id}
- cURL
- JavaScript
- Python
- Java
- Go
curl -i -X PATCH \
'https://{api_base_url_without_scheme}/rest/v1/matters/{matter_id}' \
-H 'Authorization: Bearer <YOUR_TOKEN_HERE>' \
-H 'Content-Type: application/json' \
-d '{
"title": "Review mutual NDA",
"due_date": null,
"status_id": "00000000-0000-0000-0000-000000000002",
"requester": {
"email": "requester@example.com",
"name": "Request User"
},
"main_assignee_id": "00000000-0000-0000-0000-000000000004",
"sub_assignee_ids": [
"00000000-0000-0000-0000-000000000005"
],
"custom_attributes": [
{
"custom_attribute_definition_id": "00000000-0000-0000-0000-000000000010",
"text_value": "High priority"
}
]
}'- The server URL is `{api_base_url}/rest/v1`.
You can construct the server URL using the value of `api_base_url` provided in the response when obtaining an access token.
https://{api_base_url_without_scheme}/rest/v1/matters/{matter_id}
- cURL
- JavaScript
- Python
- Java
- Go
curl -i -X DELETE \
'https://{api_base_url_without_scheme}/rest/v1/matters/{matter_id}' \
-H 'Authorization: Bearer <YOUR_TOKEN_HERE>'Request
Retrieves paginated timeline items for the specified matter. The initial supported event type is message, and public messages are returned by default. The response uses an event envelope so additional event types can be added without changing the top-level timeline item structure.
Use the page_token, visibility, and page_size query parameters to control the retrieval scope and pagination. See the parameter descriptions for details.
- Returns 404 when the matter does not exist and 403 when the caller cannot view the existing matter.
- Attachment metadata is not included in the response.
Private messages can contain sensitive information. When requesting private or all messages, ensure that external storage and forwarding preserve appropriate access controls and do not unintentionally share the content.
Use POST /matters/{matter_id}/messages to create a message.
- The server URL is `{api_base_url}/rest/v1`.
You can construct the server URL using the value of `api_base_url` provided in the response when obtaining an access token.
https://{api_base_url_without_scheme}/rest/v1/matters/{matter_id}/timeline-items
- cURL
- JavaScript
- Python
- Java
- Go
curl -i -X GET \
'https://{api_base_url_without_scheme}/rest/v1/matters/{matter_id}/timeline-items?visibility=public&page_size=50&page_token=string' \
-H 'Authorization: Bearer <YOUR_TOKEN_HERE>'OK
Timeline items matching the requested visibility.
Public timeline event type. Additional event types can be added without changing the TimelineItem envelope.
Event-specific timeline payload. The payload property corresponding to event_type is populated. The initial event type uses message.
Token for retrieving the next page. Omitted when there is no next page.
{ "timeline_items": [ { … } ], "total_size": 1, "next_page_token": "eyJjYXNlX3RpbWVsaW5lX2V2ZW50X2lkIjoiMDAwMDAwMDAtMDAwMC0wMDAwLTAwMDAtMDAwMDAwMDAwMDMwIiwidHlwZSI6Im5leHQifQ" }
Workspaces
Workspaces/folders are the common units used to store and organize resources such as contracts. This endpoint returns the workspaces/folders the calling user has access to, as a tree. For operations that target a workspace (e.g., the Contract API), specify the workspace_id obtained here. To manage workspaces across the tenant (creation, permissions, etc.), see the admin workspace operations (/spaces).