How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

LawVu Matters API

The Matters API from LawVu — 11 operation(s) for matters.

LawVu Matters API is one of 26 APIs that LawVu publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Matters. The published artifact set on APIs.io includes an OpenAPI specification and API documentation.

This API exposes 17 operations across 11 paths, and defines 44 schemas. It is described by OpenAPI 3.0.1, at version 1.0.

Requests are made against 2 base URLs: https://api-sandbox.lawvu.com/account-apis, https://api.lawvu.com/account-apis.

17 operations 11 paths 44 schemas 11 GET3 PATCH3 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.1
API Version
1.0
Base URL
https://api.lawvu.com
Resource Areas
1

Paths & Operations 17

Across 11 paths, the API surfaces 17 operations — 11 GET, 3 PATCH, 3 POST. Each is listed below with its method, path, parameters, and response codes.

Matters 17
GET
/v2/matters
Get matters
get-v2-matters 4 params → 200400
POST
/v2/matters
Create matter
post-v2-matters body → 201400409
GET
/v2/matters/{matterId}
Get matter
get-v2-matters-matterid 1 param → 200404
PATCH
/v2/matters/{matterId}
Update matter
patch-v2-matters-matterid 1 param body → 204400403404409
GET
/v2/matters/{matterId}/files/{fileId}
Get matter file
get-v2-matters-matterid-files-fileid 2 params → 200404
GET
/v2/matterTypes
Get matter types
get-v2-mattertypes 2 params → 200400
GET
/v1/matters/quickfind
Find matters
get-v1-matters-quickfind 3 params → 200
GET
/v1/matters/recent
Recent matters
get-v1-matters-recent 1 param → 200
POST
/v1/matters
Create matter
post-v1-matters body → 200
GET
/v1/matters
Get matters
get-v1-matters 11 params → 200
GET
/v1/matters/{matterId}
Get matter
get-v1-matters-matterid 1 param → 200
PATCH
/v1/matters/{matterId}
Update matter
patch-v1-matters-matterid 1 param body → 200
POST
/v1/matters/{matterId}/users
Add user to a matter
post-v1-matters-matterid-users 1 param body → 200
GET
/v1/matters/{matterId}/users
Get matter users
get-v1-matters-matterid-users 8 params → 200
GET
/v1/matters/externalid/{externalId}
ExternalId lookup
get-v1-matters-externalid-externalid 1 param → 200
GET
/v1/matters/{matterId}/fields
Get matter fields
get-v1-matters-matterid-fields 1 param → 200
PATCH
/v1/matters/{matterId}/fields
Update fields
patch-v1-matters-matterid-fields 1 param body → 200

Schemas 44

The contract defines 44 schemas that model the data the API accepts and returns. The most detailed are Matter_2 (21 properties), StatusMessage (13 properties), Matter (12 properties), File (12 properties). Each schema is shown below with its type and property counts.

AuditableReference
object
2 properties
Filtering
object
3 properties
FileType
string
The type of file entry
OperationArray
array
QuickFindMatterArray
array
FieldData
object
2 properties
MatterUser
object
12 properties
QuickFindMatter
object
9 properties
ExternalIdLookupModel
object
1 property
RecentMatterArray
array
Operation
object
4 properties
IntakeQueueReference
object
2 properties
MatterTagModel
object
2 properties
MatterFieldData
object
2 properties
FilteringArray
array
MatterTypeCollectionResponse
object
Response wrapper of a collection of items
1 property
MatterUserDataSourceResult
object
2 properties
FolderReference
object
3 properties
UpdateMatter
object
8 properties
CreateMatter
object
11 properties 1 required
CreatedMatter
object
Represents a matter that has been created
1 property
ResourceType
string
MatterStatus
string
UserFieldValue
object
File
object
12 properties
Matter
object
12 properties
TermsAndConditions
object
3 properties
UserReference
object
5 properties
CreateMatter_2
object
11 properties 1 required
MatterType
object
3 properties
ResourceReference
object
2 properties
ProblemDetails
object
6 properties
StatusMessage
object
13 properties
RecentMatter
object
7 properties
TeamReference
object
2 properties
ObjectDataSourceResultModel
object
2 properties
OptionFieldValue
object
2 properties
HttpValidationProblemDetails
object
7 properties
MatterTypeReference
object
2 properties
AssignMatterUser
object
3 properties 2 required
MatterCollectionResponse
object
Response wrapper of a collection of items
1 property
MatterManager
object
2 properties
AuditableUserReference
object
3 properties
Matter_2
object
21 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

lawvu-matters-api-openapi.yml Raw ↑

Other APIs LawVu publishes across the network.

LawVu Auth API
LawVu ContractFiles API
LawVu ContractKeyDate API
LawVu Contracts API
LawVu ContractStatusMessage API
LawVu ContractTemplates API
LawVu ContractUser API
LawVu Emails API
LawVu Features API
LawVu Fields API
LawVu Files API
LawVu Folders API
Where this information came from

This is an independent, third-party profile of LawVu Matters API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.