Skip to content

Getting started

Welcome to the AVM Greece API documentation. Use the left navigation to browse endpoints and guides.

Environments

https://appraisal-gr.realitycs.it

https://appraisal-gr-sandbox.realitycs.it

All the requests do require an OAUTH 2.0 auth token in the header, see the authentication page for details.

What the service does

The AVM (Automated Valuation Model) estimates the value of a single property in Greece from its attributes and its position. The call is self contained: you describe the property in the request and you get the estimate back, there is nothing to create beforehand and no state to keep between calls.

The service exposes a single endpoint, Valuation (AVM), which returns both the market value and the suggested asking price.

Request format

The endpoint is a POST taking a JSON body, with all the fields nested inside a Filters object:

Content-Type: application/json

{
  "Filters": {
    "latitude": 37.95140345595745,
    "longitude": 23.709728045430182,
    "contractTypeID": 1,
    "propertyTypeID": 101,
    "grossSquareFootage": 100,
    "maintenanceStatusID": 2,
    "buildYear": 1960
  }
}

Seven fields are mandatory: latitude, longitude, propertyTypeID, contractTypeID, grossSquareFootage, maintenanceStatusID and buildYear. Everything else is optional and falls back to a default, see Valuation (AVM) for the exact list.

Relation with the Italian AVM

This service mirrors AVM for the Greek market, but it is not the same API: it lives on its own host, names its fields in English camel case (propertyTypeID, grossSquareFootage) rather than in Italian, nests them under Filters, and uses its own codifications. Do not reuse an Italian payload here.

Codified fields

propertyTypeID, contractTypeID, maintenanceStatusID and energyClassID are codified: the accepted values are listed in Taxonomies.

Some optional fields are enumerations, not plain counts

unitFloor, rooms and bathrooms look like simple numbers but are capped enumerations, and the top value means "or more":

  • unitFloor starts at -1, and 0 is the ground floor.
  • rooms ranges from 1 to 6, where 6 means more than 5 rooms.
  • bathrooms ranges from 1 to 4, where 4 means more than 3 bathrooms.

Clamp your own values into these ranges before sending them, otherwise the valuation may be computed on an input you did not intend.

Response format

The response carries the valuation blocks directly, without a _metadata envelope.

  • value: estimated market value. avm is the estimate, avm_detail details it with avm_min, avm_max and the unit value avm_mq, and gross_square_footage echoes the surface used.
  • asking: suggested asking price. price is the figure, price_detail details it with price_min, price_max and the unit price price_mq.
  • uid: identifier of the valuation request that produced the response.

uid has no dashes here

The Greek service returns the uid as a plain 32 character hex string, for example 4641a6a176e0406aa1f5ef221440e97c, while other Insights services return a dashed UUID. Treat it as an opaque string.

Changes

All updates to the endpoints are tracked in the Changelog.