> For the complete documentation index, see [llms.txt](https://docs.altum.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.altum.ai/english/property-valuation-and-market/market-trend-api.md). # Market Trend API The Market Tren API analyzes real property transactions to quantify how a specific neighbourhood’s real estate market is performing today and how it has evolved over time. ## Introduction In real estate, the difference between a good decision and a costly one is **market clarity**. This API delivers that clarity by transforming raw transaction data into precise, neighbourhood-level market intelligence. Instead of relying on asking prices or assumptions, the Market Trend API reveals what properties actually sell for and how those prices are evolving over time based on historical transaction data for a given postcode. It provides clear insights into average prices, price per square meter, sales activity, and short- and long-term price trends, all segmented by property type. It also shows how prices are distributed and whether the neighbourhood is becoming more or less expensive. This API helps buyers verify whether they are paying a fair market price, enables sellers to set realistic and competitive asking prices, and allows investors to identify promising or undervalued neighbourhoods. Real estate agencies can use it to analyze local market trends with confidence, while companies and analysts can consistently compare multiple postcodes using the same reliable, transaction-based metrics. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.altum.ai/english/property-valuation-and-market/market-trend-api.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.