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

The Contracts API from LawVu — 12 operation(s) for contracts.

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

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

This API exposes 18 operations across 12 paths, and defines 42 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.

18 operations 12 paths 42 schemas 11 GET3 PATCH4 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 18

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

Contracts 18
GET
/v2/contracts
Get contracts
get-v2-contracts 4 params → 200400
POST
/v2/contracts
Create contract
post-v2-contracts body → 201400409
GET
/v2/contracts/{contractId}
Get contract
get-v2-contracts-contractid 1 param → 200404
PATCH
/v2/contracts/{contractId}
Update contract
patch-v2-contracts-contractid 1 param body → 204400403404409
GET
/v2/contracts/{contractId}/files/{fileId}
Get contract file
get-v2-contracts-contractid-files-fileid 2 params → 200404
GET
/v2/contractTypes
Get contract types
get-v2-contracttypes 2 params → 200400
POST
/v1/contracts
Create contract by upload
post-v1-contracts body → 200
GET
/v1/contracts
Get contracts
get-v1-contracts 11 params → 200
GET
/v1/contracts/quickfind
Find contracts
get-v1-contracts-quickfind 2 params → 200
GET
/v1/contracts/recent
Recent contracts
get-v1-contracts-recent 1 param → 200
GET
/v1/contracts/entities
Contract entities
get-v1-contracts-entities → 200
POST
/v1/contracts/entities
Create contract entity
post-v1-contracts-entities body → 200
GET
/v1/contracts/externalid/{externalId}
ExternalId lookup
get-v1-contracts-externalid-externalid 1 param → 200
PATCH
/v1/contracts/{contractId}
Update contract
patch-v1-contracts-contractid 1 param body → 200
GET
/v1/contracts/{contractId}
Get contract
get-v1-contracts-contractid 1 param → 200
GET
/v1/contracts/{contractId}/fields
Get contract fields
get-v1-contracts-contractid-fields 1 param → 200
PATCH
/v1/contracts/{contractId}/fields
Update fields
patch-v1-contracts-contractid-fields 1 param body → 200
POST
/v1/contracts/wizard
Create contract
post-v1-contracts-wizard body → 200

Schemas 42

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

AuditableReference
object
2 properties
Filtering
object
3 properties
ContractStatus
string
FileType
string
The type of file entry
OperationArray
array
FieldData
object
2 properties
ContractUser
object
9 properties
CreatedContract
object
Represents a contract that has been created
1 property
ExternalIdLookupModel
object
1 property
ContractTypeCollectionResponse
object
Response wrapper of a collection of items
1 property
Operation
object
4 properties
FilteringArray
array
ContractCollectionResponse
object
Response wrapper of a collection of items
1 property
ContractFieldData
object
2 properties
FolderReference
object
3 properties
CreateContract
object
11 properties 1 required
RecentContract
object
8 properties
ResourceType
string
ContractEntityArray
array
UserFieldValue
object
DataSourceResultModel
object
2 properties
QuickFindContract
object
6 properties
Contract
object
12 properties
File
object
12 properties
RecentContractArray
array
UpdateContract
object
8 properties
FileReference
object
3 properties
UserReference
object
5 properties
ContractGroupReference
object
2 properties
ResourceReference
object
2 properties
CreateContract_2
object
8 properties 2 required
ProblemDetails
object
6 properties
StatusMessage
object
13 properties
ContractEntity
object
2 properties
TeamReference
object
2 properties
ContractDetails
object
28 properties
ContractType
object
5 properties
OptionFieldValue
object
2 properties
ContractTypeReference
object
2 properties
HttpValidationProblemDetails
object
7 properties
QuickFindContractArray
array
AuditableUserReference
object
3 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

lawvu-contracts-api-openapi.yml Raw ↑

Other APIs LawVu publishes across the network.

LawVu Auth API
LawVu ContractFiles API
LawVu ContractKeyDate 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
LawVu Invoices API
Where this information came from

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