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

Landmark Document Vault API

API behind Contract Pack Vault — creates a secure, shareable container of transaction documents, adds and removes files (virus-scanned and analysed asynchronously, status Pending then Available or Quarantined), maintains property and reference details, manages the recipient organisation and its recipients, and reads the vault activity audit trail. Ten paths, version 1.0.1, OpenAPI 3.0.4. Sharing itself happens in the Contract Pack Vault web app, not the API. Billed per vault on first document added; documented rate limit 1,000 calls per minute per caller.

Landmark Document Vault API is one of 7 APIs that Landmark Information Group publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Documents, Conveyancing, and Contract Pack. The published artifact set on APIs.io includes an OpenAPI specification, an API reference, API documentation, and authentication docs.

This API exposes 10 operations across 10 paths, organized into 3 resource areas, and defines 37 schemas. It is described by OpenAPI 3.0.4, at version 1.0.1.

Requests are made against 2 base URLs: https://api.landmarkcloudservices.com/, https://uat-api.landmarkcloudservices.com/.

10 operations 10 paths 37 schemas 2 DELETE2 GET2 PATCH3 POST1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.4
API Version
1.0.1
Base URL
https://api.landmarkcloudservices.com/document-vaults
Authentication
HTTP Bearer
Resource Areas
3

Authentication & Security 1

Landmark Document Vault API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (JWT) (bearerAuth). By default, every request must be authenticated.

Paths & Operations 10

Across 10 paths, the API surfaces 10 operations — 2 DELETE, 2 GET, 2 PATCH, 3 POST, 1 PUT. They span 3 resource areas: Document Vaults, Documents, Activities. Each is listed below with its method, path, parameters, and response codes.

Document Vaults 7

Create a vault and manage its details and recipients.

POST
/
Create Document Vault
document-vault-vaults-create 1 param body → 200400401403404413429500
GET
/{documentVaultId}
Get Document Vault
document-vault-vaults-read 2 params → 200400401403404429500
PUT
/{documentVaultId}/reference
Update Reference
document-vault-reference-update 2 params body → 200400401403404409429500
PATCH
/{documentVaultId}/property
Update Property
document-vault-property-update 2 params body → 200400401403404409429500
PATCH
/{documentVaultId}/recipient-organisation
Update Recipient Organisation
document-vault-recipient-organisation-update 2 params body → 200400401403404409429500
POST
/{documentVaultId}/recipient-organisation/recipients
Add Recipient
document-vault-recipients-create 2 params body → 200400401403404429500
DELETE
/{documentVaultId}/recipient-organisation/recipients/{recipientId}
Delete Recipient
document-vault-recipients-delete 3 params → 200400401403404429500
Documents 2

Add and remove the files held in a vault.

POST
/{documentVaultId}/documents
Add Document
document-vault-documents-create 2 params body → 200400401403404413429500
DELETE
/{documentVaultId}/documents/{documentId}
Delete Document
document-vault-documents-delete 3 params → 200400401403404429500
Activities 1

Read a vault's audit history.

GET
/{documentVaultId}/activities
Get Activities
document-vault-activities-list 2 params → 200400401403404429500

Schemas 37

The contract defines 37 schemas that model the data the API accepts and returns. The most detailed are lgsAddressPAFPlus (17 properties), getDocumentVaultResponse (8 properties), individualRecipient (6 properties), activity (5 properties). Each schema is shown below with its type and property counts.

createDocumentVaultRequest
object
3 properties 1 required
createDocumentVaultResponse
object
Reference data that can be used to retrieve a Document
1 property 1 required
getDocumentVaultResponse
object
The details stored about the Document Vault
8 properties 6 required
addDocumentToDocumentVaultResponse
object
1 property 1 required
getActivitiesResponse
object
The activities relating to the associated document vault
1 property 1 required
activity
object
5 properties 3 required
lgsUuid
string
lgsUprn
integer
lgsAddressPAFPlus
object
Either buildingNumber or buildingName must be provided (both may be present).
17 properties 4 required
accountId
Your Landmark account ID - this will be provided to you during onboarding
email
string
title
string
firstName
string
middleName
string
lastName
string
teamName
string
documentVaultReference
string
Your reference that uniquely identifies the Document Vault
buyerConveyancerReference
string
The buyer's conveyancer's reference that uniquely identifies the Document Vault
recipients
array
An array of objects containing details of recipients to give access to the Document Vault
individualRecipient
object
6 properties 4 required
teamRecipient
object
3 properties 3 required
recipientsResponse
array
An array of objects containing details of recipients to give access to the Document Vault
individualRecipientResponse
teamRecipientResponse
document
object
An object containing data relating to a document
3 properties
product
object
Product information for the Document Vault
1 property 1 required
tenure
string
registered
boolean
Whether the property is registered or not
sellingCapacity
string
organisationName
string
Organisation name
productOptions
object
Product options for the Document Vault. Must contain at least one of the stated properties
3 properties
property
object
An object to provide details relating to the property. If supplied, it must contain at least one of the stated properties
2 properties
buyerConveyancer
object
An object to provide details relating to the buyer's conveyancer. If supplied, it must contain at least one of the stated properties
2 properties
propertyDetails
object
The property associated with the vault
4 properties 1 required
recipientOrganisation
object
The organisation acting for vault recipients
3 properties
recipientOrganisationResponse
object
The organisation acting for vault recipients
3 properties 1 required
lgsErrorResponse
object
4 properties 3 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

landmark-information-document-vault-api-openapi.yml Raw ↑

Other APIs Landmark Information Group publishes across the network.

Landmark Order Experience API
Landmark Conveyancing Experience API
Landmark Intelliworks APIs
Landmark Milestone Notification Service API
Landmark Planning API (powered by Barbour ABI)
Landmark Geodata Web Map Tile Service (WMTS)
Where this information came from

This is an independent, third-party profile of Landmark Document Vault 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.