generated: '2026-07-26'
method: searched
source: https://docs.api.vaultre.com.au/guide.html
also_derived_from: openapi/vaultre-api-v1-3-openapi.yml
versioning:
  scheme: uri-path minor version
  current: '1.3'
  supported:
  - {version: '1.1', base_url: 'https://ap-southeast-2.api.vaultre.com.au/api/v1.1', spec: openapi/vaultre-api-v1-1-openapi.yml, paths: 121, operations: 189}
  - {version: '1.2', base_url: 'https://ap-southeast-2.api.vaultre.com.au/api/v1.2', spec: openapi/vaultre-api-v1-2-openapi.yml, paths: 229, operations: 326}
  - {version: '1.3', base_url: 'https://ap-southeast-2.api.vaultre.com.au/api/v1.3', spec: openapi/vaultre-api-v1-3-openapi.yml, paths: 324, operations: 453}
  aggregator:
    version: '1.0'
    base_url: https://aggregator.api.vaultre.com.au/api/v1.0
    spec: openapi/vaultre-aggregator-api-v1-0-openapi.yml
    note: Versioned independently; the docs state it is "completely separate to the core VaultRE API".
  docs: https://docs.api.vaultre.com.au/guide.html
  policy: >-
    Additive-only within a minor version. Verbatim: "Within a minor version (e.g. 1.0,
    1.1, 1.2, 1.3) fields can be added to a JSON payload but we will endeavour to never
    make breaking changes (e.g. removing a field or changing a field's data type).
    Between versions, breaking changes may be made. Your application should be able to
    handle new fields being added to the JSON payload arbitrarily."
  concurrent_versions: 3
  note: >-
    All three minor versions remain published and selectable in the public Swagger UI,
    and all three specs still download with HTTP 200.
deprecation:
  policy_url: https://docs.api.vaultre.com.au/guide.html
  formal_policy: false
  sunset_header: false
  deprecation_header: false
  rfc8594: false
  note: >-
    VaultRE publishes a compatibility promise (additive-only within a minor version)
    but no formal deprecation policy: no retirement window, no end-of-life dates for
    v1.1 or v1.2, and no RFC 8594 Sunset/Deprecation headers. What stands in for a
    deprecation policy is the practice of keeping older minor versions live and
    downloadable indefinitely.
deprecated_operations: []
deprecated_operations_note: >-
  Zero operations carry `deprecated: true` in any of the four harvested OpenAPI
  documents (453 + 326 + 189 + 6 operations checked).
sla:
  url: null
  uptime_target: null
  note: No SLA or uptime commitment is published on the developer documentation site.
status_page: https://status.mrisoftware.com/
status_page_details:
  provider: Atlassian Statuspage (MRI Software group status page)
  component: Vault CRM
  verified: '2026-07-26'
  http_status: 200
  note: >-
    VaultRE has no status page of its own (status.vaultre.com.au does not resolve). The
    product is tracked as the "Vault CRM" component on MRI Software's group status page,
    which publishes per-component operational state, 90-day uptime history, incident
    reports, scheduled maintenance windows and email subscription.
changelog:
  url: https://docs.api.vaultre.com.au/changelog.html
  artifact: changelog/vaultre-changelog.yml
  most_recent_entry: '2026-05-29'
support:
  contact: api@vaultre.com.au
  registration: https://www.mrisoftware.com/au/products/vault/api-integrations/
roadmap:
  url: null
  note: No public API roadmap is published.