Chargement...
Chargement...
Arrange integration with our team
Integrate an indicative Luxembourg apartment estimate into your workflow. Review the data, assumptions and limits before using results in a credit decision.
Request accessThe /api/v1/estimation API uses the public estimator's calculation: a municipal reference and internal adjustments. It supports freehold apartments, existing or off-plan when segment data is available.
The currently integrated references come from the Housing Observatory publications of 25 June 2026. Unavailable prices are not replaced with fictional individual sales.
The range is conventional, with no measured statistical accuracy. The result is neither a signed appraisal, a TEGOVA-certified market value nor a financing decision.
Try the public calculatorUse a server API key in Authorization: Bearer or X-API-Key. Do not expose it in public browser code. The example below uses the actual accepted field names.
POST https://tevaxia.lu/api/v1/estimation
Authorization: Bearer YOUR_API_KEY
Content-Type: application/json
{
"commune": "Luxembourg",
"typeBien": "appartement",
"surface": 85,
"nbChambres": 2,
"etage": "adjEtage2e3eRef",
"etat": "adjEtatBonRef",
"exterieur": "adjExtBalconRef",
"parking": false,
"classeEnergie": "D",
"estNeuf": false
}A successful response contains success, data and meta. data includes estimationCentrale, estimationBasse, estimationHaute, prixM2Base, prixM2Ajuste, sourceBase and ajustements. meta describes the method and limits; no comparable-sale count, recommended LTV or certified MLV is returned.
Handle errors: 400 for invalid requests, 401 for authentication, 404 when no estimate is available, 429 for call limits and 500 for server errors.
Read the API documentationThe legacy /api/v1/mlv path calculates arithmetic sensitivity to entered reductions. Its mlv and ratioMLVsurMV fields describe this scenario only; ltvBands is empty and the result is marked non-regulatory. It does not validate CRR requirements or risk weights.
Review the valuation methodsCheck your use cases, required data, error handling and human review. An address alone does not provide all the characteristics needed for an estimate.
Logging for database-managed keys records the key identifier, endpoint, status, call duration and last use. This description is not a general privacy guarantee: processing scope, retention and service providers must be documented contractually.
Agree availability, response times, hosting, quotas and service commitments before integration. No numerical performance or guaranteed update frequency is stated here.