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

VaultRE Clearing Sales Properties API

Operations related to clearing sales properties

VaultRE Clearing Sales Properties API is one of 50 APIs that VaultRE publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

The published artifact set on APIs.io includes an OpenAPI specification, an API reference, API documentation, a getting-started guide, authentication docs, and code examples.

This API exposes 5 operations across 3 paths, and defines 58 schemas. It is described by OpenAPI 3.2.0, at version 1.3.

Requests are made against a single base URL, https://ap-southeast-2.api.vaultre.com.au/api/v1.3.

5 operations 3 paths 58 schemas 3 GET1 POST1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.3
Base URL
https://ap-southeast-2.api.vaultre.com.au/api/v1.3
Authentication
API Key, HTTP Bearer
Contact
Resource Areas
1

Authentication & Security 2

VaultRE Clearing Sales Properties API declares 2 security schemes for authenticating requests. An API key is passed in the header as X-Api-Key (Api-Key). It accepts HTTP bearer tokens (Bearer).

Paths & Operations 5

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

clearingSalesProperties 5

Operations related to clearing sales properties

GET
/properties/clearingSales/sale/sold
Retrieve a list of sold clearing sales properties
getClearingSalesSoldProperties 28 params → 200
GET
/properties/clearingSales/sale
Retrieve a list of clearing sales properties
getClearingSalesProperties 24 params → 200
POST
/properties/clearingSales/sale
Add a clearing sales property
addClearingSalesProperty body → 201400
GET
/properties/clearingSales/sale/{id}
Retrieve a single clearing sales property
getClearingSalesProperty 1 param → 200
PUT
/properties/clearingSales/sale/{id}
Update a clearing sales property
updateClearingSalesProperty 1 param body → 200400

Schemas 58

The contract defines 58 schemas that model the data the API accepts and returns. The most detailed are SaleHistory (44 properties), Property (37 properties), AddUpdateProperty (29 properties), User (20 properties). Each schema is shown below with its type and property counts.

ID
object
1 property
Rate
object
2 properties
Geolocation
object
3 properties
ClearingSalesSoldProperty
Portal
object
2 properties
Urls
object
3 properties
OfficeReferral
object
1 property
AuctionDetails
object
3 properties
PropertyPhoto
object
13 properties
PropertyFile
object
9 properties
AccountBranch
object
5 properties
AddUpdateClearingSalesProperty
PreDistributionDeduction
object
2 properties
SaleHistory
object
44 properties
Area
object
2 properties
TenderDetails
object
1 property
Region
object
2 properties
ContactSearchResult
object
9 properties
Property
object
37 properties
CommissionSplitDeduction
object
2 properties
CustomAddress
object
4 properties
RoyalMail
object
13 properties
ResidentialProperty
MarketingUser
object
2 properties
PropertyType
object
3 properties
OfficeDeduction
object
2 properties
SuccessOrError
object
3 properties
Country
object
4 properties
CommissionSplit
object
12 properties
ContactMinimal
object
6 properties
PhoneNumber
object
4 properties
SetSaleDateDetails
object
1 property
Address
object
9 properties
ServiceChargeFrequency
object
2 properties
Suburb
object
6 properties
PropertyPhotoThumbnails
object
2 properties
ExternalLink
object
4 properties
AddUpdateExternalLink
object
2 properties
Access
object
4 properties
State
object
3 properties
SharedOwnership
object
3 properties
CommissionSplitType
object
2 properties
SoldType
object
2 properties
AddUpdateProperty
object
29 properties
PropertyKey
object
10 properties
User
object
20 properties
PortalAccess
object
4 properties
PropertyClass
object
3 properties
ClearingSalesPropertyExtended
District
object
3 properties
ClearingSalesProperty
AddUpdateSaleProperty
object
19 properties
AddUpdateResidentialProperty
UpdateAddress
object
5 properties
FeesCharges
object
2 properties
UserPhoto
object
2 properties
Building
object
2 properties
ExternalLinkType
object
2 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

vaultre-clearingsalesproperties-api-openapi.yml Raw ↑

Other APIs VaultRE publishes across the network.

VaultRE Advertising API
VaultRE Aml API
VaultRE Buildings API
VaultRE Bulk API
VaultRE Business Properties API
VaultRE Calendar API
VaultRE Campaigns API
VaultRE Categories API
VaultRE Commercial Properties API
VaultRE Conjunctionals API
VaultRE Contacts API
VaultRE Corelogic API
Where this information came from

This is an independent, third-party profile of VaultRE Clearing Sales Properties 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.