> 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-data/move-data.md).

# Move data API

Move Data API will fetch different statuses for the objects on the market.

## Introduction

The Move data API is a comprehensive tool that offers in-depth insights into real estate listings and market trends based on zip code-level data. It is designed to support a broad array of applications, from market analysis to personalized property searches.

Here’s a closer look at what the Move data API offers:

* **Property listing retrieval**: By inputting an address, users can obtain current listing information for a specific property, gaining immediate access to its status in the real estate market.
* **Pertinent property data**: The API provides details on up to five significant properties in a chosen zip code area, which can be filtered to show either owned or rented units. This feature is invaluable for comparative market analysis and for users interested in local real estate landscapes.
* **Market data overview**: Users can also gather data on the aggregate number of properties listed for sale or rent within any given zip code, offering a macro view of market availability and activity.

The Move data API is an essential resource for real estate professionals, investors, and market analysts looking for accurate and up-to-date property information and market dynamics to make informed decisions.


---

# 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-data/move-data.md?ask=<question>&goal=<user_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.