API documentation for LegalOn services
LegalOn API (1.1.0)
- 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/contracts/{document_id}
- cURL
- JavaScript
- Python
- Java
- Go
curl -i -X DELETE \
'https://{api_base_url_without_scheme}/rest/v1/contracts/{document_id}' \
-H 'Authorization: Bearer <YOUR_TOKEN_HERE>'- 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/contracts/{document_id}/versions
- cURL
- JavaScript
- Python
- Java
- Go
curl -i -X GET \
'https://{api_base_url_without_scheme}/rest/v1/contracts/{document_id}/versions' \
-H 'Authorization: Bearer <YOUR_TOKEN_HERE>'{ "document_id": "00000016-0000-0000-0001-100000000001", "versions": [ { … }, { … } ] }
Update contract information request payload
Contract metadata update request payload. This schema accepts metadata fields updated by the document metadata update source and document_status_code. Omit document_status_code to keep the current status. Set NONE to clear the current status.
Contract category, position, and governing law classifications
- 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/contracts/{document_id}/versions/{document_version_id}
- cURL
- JavaScript
- Python
- Java
- Go
curl -i -X PATCH \
'https://{api_base_url_without_scheme}/rest/v1/contracts/{document_id}/versions/{document_version_id}' \
-H 'Authorization: Bearer <YOUR_TOKEN_HERE>' \
-H 'Content-Type: application/json' \
-d '{
"metadata": {
"title": "Confidentiality Agreement",
"language_code": "en",
"own_parties": [
"LegalOn Technologies, Inc."
],
"counter_parties": [
"Example Corp."
],
"contract_category_positions": [
{
"category_code": "NDA",
"position_code": "discloser",
"governing_law_code": "JP"
}
],
"document_status_code": "INTERNAL_DRAFT"
}
}'{ "document_id": "00000016-0000-0000-0001-100000000001", "document_version_id": "00000016-0000-0000-0001-100000000101", "version_number": 3, "updated_at": "2026-05-08T03:13:20Z", "title": "Confidentiality Agreement", "language_code": "en", "document_status_code": "INTERNAL_DRAFT", "own_parties": [ "LegalOn Technologies, Inc." ], "counter_parties": [ "Example Corp." ], "contract_category_positions": [ { … } ] }
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).