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 Files API

The Files API from LawVu — 9 operation(s) for files.

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

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

This API exposes 14 operations across 9 paths, and defines 22 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.

14 operations 9 paths 22 schemas 2 DELETE5 GET2 PATCH4 POST1 PUT

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 14

Across 9 paths, the API surfaces 14 operations — 2 DELETE, 5 GET, 2 PATCH, 4 POST, 1 PUT. Each is listed below with its method, path, parameters, and response codes.

Files 14
GET
/v2/files/{fileId}
Get file
get-v2-files-fileid 1 param → 200404
DELETE
/v2/files/{fileId}
Delete file
delete-v2-files-fileid 1 param → 204403404
PATCH
/v2/files/{fileId}
Update file
patch-v2-files-fileid 1 param body → 204400403404409
POST
/v2/files/{fileId}
Upload file version
post-v2-files-fileid 1 param body → 201400404409
GET
/v2/files/{fileId}/content
Get file content
get-v2-files-fileid-content 1 param → 200404
POST
/v2/files
Create file
post-v2-files body → 201400409415
GET
/v1/files
Get files
get-v1-files 11 params → 200
GET
/v1/files/{fileId}
Get file
get-v1-files-fileid 1 param → 200
DELETE
/v1/files/{fileId}
Delete file
delete-v1-files-fileid 1 param → 200
PATCH
/v1/files/{fileId}
Patch file
patch-v1-files-fileid 1 param body → 200
GET
/v1/files/{fileId}/download
Download file
get-v1-files-fileid-download 1 param → 200
POST
/v1/files/{fileId}/move/{destinationId}
Move file
post-v1-files-fileid-move-destinationid 3 params → 204
POST
/v1/files/{targetType}/{targetId}
Upload file
post-v1-files-targettype-targetid 2 params body → 200
PUT
/v1/files/{targetType}/{targetId}/uploads/{uploadId}
Finalise upload
put-v1-files-targettype-targetid-uploads-uploadid 3 params body → 200

Schemas 22

The contract defines 22 schemas that model the data the API accepts and returns. The most detailed are FileDetailModel (17 properties), CreateFolder (12 properties), File (12 properties), FileListItem (12 properties). Each schema is shown below with its type and property counts.

AuditableReference
object
2 properties
FileDetailModel
object
17 properties
UpdateFile
object
2 properties
FileType
string
The type of file entry
OperationArray
array
Operation
object
4 properties
FinaliseUploadModel
object
5 properties
UploadFilesRequest
object
3 properties
FileListItem
object
12 properties
FolderReference
object
3 properties
ResourceType
string
File
object
12 properties
UserReference
object
5 properties
ResourceReference
object
2 properties
FileListItemDataSourceResult
object
2 properties
ProblemDetails
object
6 properties
FileUploadResourceType
string
CreateFolder
object
Request model for creating a folder
12 properties 2 required
UploadedFile
object
Represents a file that has been uploaded
1 property
HttpValidationProblemDetails
object
7 properties
AuditableUserReference
object
3 properties
UploadFileForm
object
4 properties 2 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

lawvu-files-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 Folders API
LawVu Invoices API
Where this information came from

This is an independent, third-party profile of LawVu Files 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.