Changelog

Changes that affect integrations are listed here, newest first. Breaking changes ship under a new API version; additions and fixes ship in v1.

October 2026

Public API documentation

The Vestta API now has its own documentation site, with guides, an endpoint reference generated from the OpenAPI schema, and Swagger UI.

Property responses only contain public data

List properties and Retrieve a property now return the same set of fields, all of them documented in the property object.

• Internal fields are no longer returned: internal notes, owner and agency links, capture details and source; in specs, the commission, captation and VAT figures, price history, portal settings and internal flags.
• specs only contains documented listing characteristics; images and videos only their public playback fields, and only processed videos.
• Location follows the property's address privacy: exact for public addresses, rounded to about 1 km for approximate ones, and only the municipality for hidden ones. Map-area filters use the same published coordinates.
• Both endpoints now return title, country, created_at and updated_at.

Lead responses only contain contact and search data

List leads returns the lead's identity, contact details, status and search preferences. Internal notes, ID documents, rating and scoring, the assigned agent, capture details, follow-up dates and internal IDs are no longer returned, and internal notes are removed from search_preferences.

Error messages no longer include internal details

Create an inquiry answers 409 Lead already exists, 400 Lead could not be created and 500 Error creating lead inquiry instead of database or exception text.

Schema published only on this site

The API no longer serves its own reference pages or openapi.json. The schema is published at /openapi.json on this site.